Solved

server 2003 client login problem

Posted on 2013-06-18
12
327 Views
Last Modified: 2013-07-02
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.
0
Comment
Question by:hvserv
  • 8
  • 4
12 Comments
 

Author Comment

by:hvserv
ID: 39256336
Here is the screenshot
phelps.jpg
0
 
LVL 9

Expert Comment

by:MHMAdmins
ID: 39256437
You may have to take the machines off of the workgroup and re-add them to re-establish connection and credentials.
0
 

Author Comment

by:hvserv
ID: 39256447
I'll try that - any idea why the odd machine name shows up at the top of the dialog box?
0
 
LVL 9

Expert Comment

by:MHMAdmins
ID: 39256457
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
 

Author Comment

by:hvserv
ID: 39256522
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
 
LVL 9

Accepted Solution

by:
MHMAdmins earned 500 total points
ID: 39256541
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
Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

 

Author Comment

by:hvserv
ID: 39256642
I can access the server by local IP in remote desktop.  user credentials work fine there - but not from local desktop.
0
 
LVL 9

Expert Comment

by:MHMAdmins
ID: 39256654
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
 

Author Comment

by:hvserv
ID: 39256729
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
 

Author Comment

by:hvserv
ID: 39256771
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
 

Author Comment

by:hvserv
ID: 39293521
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
 

Author Closing Comment

by:hvserv
ID: 39294420
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

Featured Post

Too many email signature changes to deal with?

Are you constantly being asked to update your organization's email signatures? Do they take up too much of your time? Wouldn't you love to be able to manage all signatures from one central location, easily design them and deploy them quickly to users. Well, you can!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Many admins will agree: WSUS is is a nice invention but using it on the client side when updating a newly installed computer is still time consuming as you have to do several reboots and furthermore, the procedure of installing updates, rebooting an…
Learn about cloud computing and its benefits for small business owners.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …

943 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now