Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

domain not available

Status
Not open for further replies.

Southerndiva

IS-IT--Management
May 15, 2002
31
TT
I have a very small network. The server's OS is Win2k Server. All the workstations run WinXP. The protocol is TCP/IP. I can access the server from all machines except one. Everytime i try to access the domain the error is - domain is not available. it is. because the other machines are able to access. i checked the cabling. everything is intact. what else should i check? it is extremely frustrating.

Thank you in advance.

ps - yesterday i was able to access the server. the only thing that changed is that i turned off the w/station last nignt
 
maybe the machine account in the domain became corrupted. Try removing it from domain membership, rebooting, and re-adding it to the domain.
 
Check username; password (caps lock could be on)

Make sure patch cable is pluged and it snaps when you plug it in.

make sure you are loggin onto the domain and not he local computer.
 
I have the same problem...

Some of my workstations, wont log on to others, depending on their mood. A reset is normally enough to fix the problem, but really..

One clue I noticed originally, was that only some of the domain user/admin accounts worked, and the others gave the 'domain not available' message on bootup. My machines were XP too now I think about it...

I thought perhaps it was because my Win 2k server was min.specs (not very wise), but realistically on a 4 PC network, how much work can it be doing....

And its not the cabling, addressing, useraccounts etc, It must be the way the server/client stores or asks for authentication. An active directory thang...
 
I know MS changed a lot on XP, but if you go to command prompt on the machines that don't find the domain, type ipconfig /all and route print and see what you get. Also, running DHCP? I'm guessing your running XP Pro, since the home edition has little or no networking. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"Don't take a fence down until you know why it was put up".
Robert Frost (1874 - 1963); U.S. poet.

 
Have you completed the basic troubleshooting steps? Check connectivity, inspect event logs, look for hardware failure, etc... Take a really close look at your DNS config both on the workstation and on the server, from experience that type of errors is usually related to DNS being unavailable or not configured corerctly.
 
Hi Southerndiva,

check the Network Properties..IP/WINS on the XP box and make sure that NetBios is set as Standard...with it activated it can cause problems like you suggest.

Paul
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top