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 biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem using run: \\name, but \\ip works. Win2k3/XP 1

Status
Not open for further replies.

ATLMatt

Technical User
Jun 18, 2007
94
US
Problem:
Users attempting to access a specific server over the LAN or WAN using run: “\\servername” and “\\servername\sharedfoldername” get an error stating that “\\servername is not accessible... You might not have permission... Contact an admin... Login failure: The Account name is incorrect”. However, you can connect using run: “server ip” or “\\server ip\sharedfoldername”.
I notice that on the client machines under event view:system there is an error stating:

“The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/servername.domainname.com. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (DOMAINNAME.COM), and the client realm. Please contact your system administrator”

I am not sure if this is the root of the problem, but so far it is the only thing that I have noticed that struck me as odd, and I am assuming it is related.

I only get this error once in the log, but I get it around the time of the first attempted access to the server. On several of the machines, using cmd: ipconfig /flushdns and then restarting the PC fixed the problem temporarily, but the issue returned the next day. The server is running Win2k3, the clients are all WinXP Pro. I have a couple of other servers that don’t have the issue, just this one which is the primary server. Thanks for any help or ideas on what to look for, I’ve had a lot of trouble tracking anything down so far.
 
Do you have a load of reverse lookup records for the same machine name on the DNS server? Could be cacheing a bad name and thus causing that problem.
 
Sorry I meant to say an ip that is no longer used for the particular computer name.

A way to remedy this (if it is and you may already be doing this) is to look up on aging and scavenging
 
It looks like the problem was with active directory and WINS replication due to a misconfigured NIC on one of the servers. WINS was failing/sending an incorrect IP. With that IP removed and the NIC reconfigured the problem seems to be gone, WINS is replicating propperly now. I'm not 100% on that explanation, but so far everything looks good.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top