Re: I really screwed up this time!

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 09/24/05 

Date: Sat, 24 Sep 2005 13:27:58 -0400

In news:bIqdnYiKZcH3G7LeRVn-sg@comcast.com,
R. P. <r_pol12gar@hotmail.com> typed:
> "Shenan Stanley" <newshelper@gmail.com> wrote:
>> When you change the "radio button" to Domain from workgroup, you
>> should enter the FQDN (excluding the workstation name) in the domain
>> field.. i.e.: region.nos.company.com (However - if your DNS is setup
>> correctly on your laptop, whatever you saw when logging in would be
>> fine.. For example, if in the DOMAIN fiel in the logon box you saw
>> "REGION", then you could enter that in the DOMAIN field when leaving
>> the workgroup for the domain.)
>>
>> When it asks for the username, your username should be the DOMAIN
>> name backslash your username: REGION\Username.
>> (Since you are not a member of the domain yet - you need to tell the
>> authenticating system you are logging in as the DOMAIN user and not
>> the local user of that computer - although it may work out either way
>> for you.)
>>
>> On top of all that - you must be logged into the laptop as a local
>> administrator.
>
> Well, my company's PC Support guys fixed the problem today. Apparently
> each PC has a special Administrator account and password that allows
> them to log into it even if users like me screw things up.

There's a built-in administrator account and password in NT based operating
systems. Most IT folks don't like to grant end-users admin rights over their
computers because it's so easy for mistakes like this to happen. You aren't
the first, and you surely won't be the last, to do this. However, you are
unlikely to do this again yourself, I imagine! :)

> Next I'm
> going to try out Malke's suggestion to map my printer attached to the
> desktop PC's LPT1 port to the laptop.

Probably not necessary anyway - add a printer, choose network type, browse
to the computer to which it's attached, and select the printer. No need to
use LPT ports.

> Frankly, I've never seen this
> "net use" command before because our company printers were all on the
> network with their own IP addresses.

No matter how you're trying to use your home network's printer, you'll
likely still have the same problem printing to it, because of the VPN....if
my surmisal (that's a word, right??) is correct, they're blocking all
traffic except that which goes from your laptop to the company network when
the tunnel is enabled. This keeps creepy crawlies from getting into your
perhaps unsecured home network, and into theirs. Hence my suggestion to
connect the printer directly when needed.
>
> Thanks for all the tips you guys gave me. Thanks to you, these MS news
> groups are an invaluable resource.
>
> Rudy

They sure are.