On Thu, 2007-04-05 at 11:45 -0700, piclist@mmendes.com wrote:
> I'm not sure the domain networking will not work.  I don't have any Vista
> machines here at work where we do use domains so I can't test this right away
> and I don't use a domain at home, so it won't be easy to test it there either.
> But if you follow the instructions I gave in another post, I'd be 
> willing to bet
> that you can use "net use" to map network drives in a domain just like in a
> workgroup environment simply by providing the appropriate "domain\user"
> credentials in the command line.

Yes, I believe that would work, but you loose everything else that makes
"domain" type logins so appealing to companies. At the minimum, any
scripts IT wants run on your machine at login won't run, since you're
not logging in (this however might be a good thing, depending on how you
look at things...).

Aside from that, most resources on the network that require a "logged
into the domain" computer won't speak to you (since your machine isn't
"trusted"). It all depends how your IT has set up your network.

I know in my case most of "public internet" stuff, and file sharing
works fine, but none of the more "internal" stuff will work unless your
machine is "logged into the network" (heck even trying to connect to the
exchange server for email doesn't work, you'd be stuck with OWA, pretty
useless).

The fact is, if you want to avoid headache and log in to your companies
domain, you have to spend, spend, spend with Mickeysoft.

TTYL

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist