credentials conflict and/or cannot find domain

[nchrist]

ok...let me see if i can condense this problem down. w2k pc was--out of the blue--having problems connecting to the server. in the process of trying to figure out what was wrong i went to system-network id-properties and tried to re-connect to domain. WRONG!! the only thing i could do to get out of it was put in a workgroup. i used the same name as the domain. WRONG!! now i can't even get a "log on to" line when i sign on the computer.

oh, and by the way, the reason my pc was having trouble connecting to the w2k server was because after loading some updates to the w2k server my DHCP server was not starting. got this problem solved.

now back to the pc...i've renamed it a couple of times...checked the server and it was showing up...re-booted--server and pc...ran ipconfig /all...all information looks good...try to run network id and get the message "domain can not be found". if i map the drives to the server then i get the message "credentials conflict".

i've removed the 3com card re-booted and ran fix w2k. shutdown re-installed 3com. same problem.

any suggestions

tks
n

 

[Cwgunder]

Have you checked the Microsoft client? Secificaly, Client for Microsoft Networks. You may want to remove and re-install that client. Also, removeing and re-installing TCP/IP might help.

I've seen some spyware that has been successfully able to screw up winsock. I found a utility that repaired this pproblem for me the last time I ran into this. It can be found at:

http://www.softpedia.com/get/Tweak/Network-Tweak/WinSockFix.shtml

After doing these three things, I'd then attempt to add it back to the domain. I'm fairly sure you need to authenticate with a domain account in order to use your map drives.

Let me know how it turns out for ya!


Hope this helps

Good Luck!

Chris

 

[nchrist]

Chris, tks for the tips, unfortunately they did not work. I tried them forwards, backwards, sideways and around and could not get it to fix my problem. I have finally resorted to calling the local IT shop that originaly set up our server. Maybe they can come up with the solution.

tks for tyring

n