server 2003 client login problem

I have (2) XP Pro users that regularly log into a 2003 file server (in a workgroup).  Both machines now fail to do so (credentials were saved and are the same as client machine login).  I can ping the server, see all other network resources, log in to other servers, but not the server in question.  Cannot log in as administrator.  Screen shot shows odd condition - note windows shows "connecting to phelps," which is the name of the server.  Note title of dialog shows "RECP2" which is another (windows 7 Pro) machine on the network.  The RECP2 machine never accesses phelps.  Other users on the network can access the phelps.
hvservAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
MHMAdminsConnect With a Mentor Commented:
Try access the UNC path with the IP address and not the DNS name. If you are able to it might be a DNS or host file issue.
0
 
hvservAuthor Commented:
Here is the screenshot
phelps.jpg
0
 
MHMAdminsCommented:
You may have to take the machines off of the workgroup and re-add them to re-establish connection and credentials.
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
hvservAuthor Commented:
I'll try that - any idea why the odd machine name shows up at the top of the dialog box?
0
 
MHMAdminsCommented:
It might be that someone cached that connection by manually connecting to the other pc name. To be honest I couldn't tell you without actually looking at the setup of the network/
0
 
hvservAuthor Commented:
took one of the machines out of the workgroup, restarted, put it back in, restarted, exactly the same symptoms.  I did notice that the RECP2 label only shows up in the dialog title if I try to go directly to \\phelps from "run."  All mapped drives, etc. show correct title when login appears for them, but they do not connect.
0
 
hvservAuthor Commented:
I can access the server by local IP in remote desktop.  user credentials work fine there - but not from local desktop.
0
 
MHMAdminsCommented:
Go to control pannel, user account and see if you can manage credentials of the user profile and delete cached credentials. In windows 7 it's under credential manager where it stores cached credentials.
0
 
hvservAuthor Commented:
XP machines - but I went to user anddeleted server credentials.  Recreated them.  No improvement.  Machine has a local admin account - I can log into phelps from within that account on the problem machine.  If I switch back to the problem user, on the problem machine, I cannot log in to phelps with any credentials, including the ones I just used in the local admin account.
0
 
hvservAuthor Commented:
I went to another machine, in a different workgroup, and successfully logged into phelps using the user credentials from the problem machine.  It looks like the problem has to do with the local user.  What is strange is that (2) users, on different machines, started experiencing identical problems at the same time.  Similarly configured users on other machines (XP and 7) are not affected.
0
 
hvservAuthor Commented:
have spent some more time pursuing this - when xp clients try to log on to the server they get the following error:

"\\phelps    You were not connected bacause a duplicate name exists on the network.  go to system in control panel to change the name an try again."

There is no duplicate name on the network.  However, when I shut down the RECP2 machine
and restart or renew the local address for the xp client, it can connect.  It would seem that the RECP2 machine is somehow appearing as phelps on the network but I can't figure out how or how to disabuse my router (which is acting as a DNS proxy) of that notion.  Incidentally, I can ping phelps from the xp workstations successfully, by name.
0
 
hvservAuthor Commented:
It was a host file issue.  Some older workstations has an old address for phelps in the host file.  The old address wasn't an issue until DHCP shoved a new machine (in this case RECP2) down onto that address.  Sort of russian roulette as things had been stable for months with the occasional new machine coming online and older ones leaving.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.