Domain at work, Cable modem at home

[dhborchardt]

I have a T43 that I use on an Active Directory Domain at work. I also bring it home and use it on my cable modem. In order to use it on the cable modem I have had to remove it from the domain and make it a workgroup, also I need to change the DNS settings to obtain atuomatically. When I retrun to work I need to get it back into the domin which requiers an Admin login.
Is there some way to automate this?
Can the same username be used on the domain and off?

Thanks

[Hammerstein]

You could try the program here - http://www.globesoft.com/

I suspect it might be possible to automate via the 'netsh' command line utility hidden in XP Pro, but I'm not sure exactly how to go about switching Domains that way. Sorry, but it should likely be possible.

[dhborchardt]

Thanks
I was curious if anything should even be nessesary. I would think that since it saw that there is no domain to connect to, it would just use the alternate config for the tcp settings and automatically grab a private IP. Maybe this is not how the alternate config works.

[jdhurst]

If you are running XP Pro, it should not matter that you are on a Domain at work, except if at work they have you on a Proxy Server and/or a static IP address. You can try using Access Connections to set different profiles for home and office. Office can have static IP, set DNS, etc. wheres Home can be more vanilla. This is what A/C is for, and in your case, it may help. ... JD Hurst

[dhborchardt]

Thanks
Access Connections is what I need.

[mappler]

Looks like you are on the right path. I use my laptop exactly as you do (Domain at work and cable modem at home) and everything works perfectly. Post back if you have more trouble.

-Matt

[bill bolton]

> I use my laptop exactly as you do (Domain at work and cable modem
> at home) and everything works perfectly.

Same here... in my field work I also use my T41 on a whole bunch of LANs besides the one my corporate SOE is configured for. Access Connection is wonderful for managing connectivity in a variety of differing LAN environments!

Cheers,

Bill

[Razorback]

It may be that the AD domain's group policy does not allow logging on to the machine if the domain is unavailable. That would be a setting imposed by the domain admins.

Are you able to log on to your machine with the domain account when completely disconnected from a network?

Greg

[mikek5117]

We have a Microsoft Small Business Server at work with a domain structure. My domain login works on my Thinkpad (as well it did on my previous computer) using the domain login at all times regardless if I am connected to the network or not. Now that only gets you into the computer, with my old Dell then Windows XP networking would connect me to the wired network at work, and my wireless network at home. Sharing resources at home was a hassle because I could never get it to find the home workgroup based network. The IBM Access Connections works basically the same way connecting to a list of networks in order of preference, however I still have not tried to set up a true peer-to-peer network at home to see if it will see the other resources or not. However, bottom line is that domain based network at work is fully functional and internet at home or other WiFi spots works fine.

[Razorback]

Again, this may be a policy imposed by the administrator of the domain. While not the default, it can certainly be done a couple of ways.

In the old days of NT (and should work for 2000 and XP), change HKLM\Software\Microsoft\Windows NT\CurentVersion\Winlogon\CachedLogonsCount to 0 to prevent a logon using a domain account if the domain is not available.

With AD, the group policy setting that defines this is Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > Interactive Logon: Number of previous logons to cache (in case domain controller is not available.) If this value is set to 0, you cannot logon using a domain account if the domain is not available.

This of course makes the notebook fairly unusable when disconnected from the domain. I would visit with the admin(s) of the domain and see if this setting was applied in error.

Greg