rtlaw
asked on
Logon failure: The target account name is incorrect Windows 2000 machine gets event 3034 and windows 2003 server gets event id 529 - I can't connect using unc, but can via IP
I have a windows 2000 server that I am trying to map a drive to on a windows 2003 server. I can reach the administrative shares on the windows 2003 server via IP address, but can not access them via \\servername\c$
From the client I get a message that says Logon failure: The target account name is incorrect and a series of event id 3034 saying "the redirector was unable to initialize security context or query context attributes."
On the windows 2003 server I am attempting to connect to the event log gets an error in the security section of the event viewer event id 529 saying unknown username or bad password.
I can't figure it out.. Most other servers can connect fine.
NSLOOKUP gives the proper address
Ping gives the proper address
IPconfig /registerdns has been done
Everything looks ok, but it sure doesn't work..
the user id password combination is the same as being used on other machines.
The host machine is not a domain controller, just a normal windows server.. It does however host exchange and other file shares.
From the client I get a message that says Logon failure: The target account name is incorrect and a series of event id 3034 saying "the redirector was unable to initialize security context or query context attributes."
On the windows 2003 server I am attempting to connect to the event log gets an error in the security section of the event viewer event id 529 saying unknown username or bad password.
I can't figure it out.. Most other servers can connect fine.
NSLOOKUP gives the proper address
Ping gives the proper address
IPconfig /registerdns has been done
Everything looks ok, but it sure doesn't work..
the user id password combination is the same as being used on other machines.
The host machine is not a domain controller, just a normal windows server.. It does however host exchange and other file shares.
ASKER
It is not a CD, it is a standard terminal server/citrix server.. It actually is affecting more than 1 server as well.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This EE link describes a similar condition (via IP works, via UNC does not)
Have you seen / tried this fix? http://tinyurl.com/r9m8c