Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Cannot connect to domain controller
Message
From
18/02/1999 15:17:58
 
 
To
18/02/1999 08:52:36
Christine Bieri
Center For Genome Research
Montréal, Quebec, Canada
General information
Forum:
Windows
Category:
Networking & connectivity
Miscellaneous
Thread ID:
00188818
Message ID:
00189009
Views:
16
>I get the following message when trying to log on to any machine on my domain. (NT server 4.0, with 4.0 workstations)
>
>"A domain controller for your domain could not be contacted. You have
>been logged on using cached account information. Changes to your
>profile since you last logged on may not be available."
>
>Any ideas on what causes this? Everything was working fine yesterday, nothing has been changed, there have been no power failures, and I can't see anything that would make the domain controller (my server I imagine?) not visible to the other machines.
>

If you're using TCP/IP to connect to the server, and DHCP (IOW, your machine gets an IP address assigned each time it connects to the net, as opposed to a static IP address, which is assigned permanently to a single machine) it's possible that either (1) there are no free IP addresses available for the DHCP server to assign (IOW, there are more machines than available IP addresses controlled by the DHCP server), or (2) the DHCP server or service is down or disabled.

Ed
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform