Network Access Issues

[Kris Sokolowski]

I am looking into a problem that has only recently appeared on a system we
support. The system consists of 2 W2K servers, one is the PDC with DNS, the
second is the BDC. We have recently had users reporting that they are unable
to map to a drive from their workstations to a file share on the PDC. The
message they get is 'The target account name is incorrect'. This only
appears if they try to map it using \\servername\map, if they use
\\ipaddress\map then the map works. The users are also getting a problem
when trying to print via the PDC which acts as a print server. When they try
to print they get the message 'Access is denied. Unable to connect'.

This appears to be happening to users who connect via the PDC. Users connect
via the BDC and who map to file shares on the BDC mad print via printers
controlled by the BDC are OK.

I have tried to map a network drive from the BDC to a share on the PDC and
get the 'The target account name is incorrect' message, whereas I can map to
share on the BDC from the PDC.

Any ideas.

Thanks.

 

[Kevin D. Goodknecht]

In

I am looking into a problem that has only recently appeared on a
system we support. The system consists of 2 W2K servers, one is the
PDC with DNS, the second is the BDC. We have recently had users
reporting that they are unable to map to a drive from their
workstations to a file share on the PDC. The message they get is 'The
target account name is incorrect'. This only appears if they try to
map it using \\servername\map, if they use \\ipaddress\map then the
map works. The users are also getting a problem when trying to print
via the PDC which acts as a print server. When they try to print they
get the message 'Access is denied. Unable to connect'.

This appears to be happening to users who connect via the PDC. Users
connect via the BDC and who map to file shares on the BDC mad print
via printers controlled by the BDC are OK.

I have tried to map a network drive from the BDC to a share on the
PDC and get the 'The target account name is incorrect' message,
whereas I can map to share on the BDC from the PDC.

Any ideas.

Thanks.

Win2k only has domain controllers the term PDC and BDC went away with NT4 on
NT4 only the PDC had writable database and the BDC had a read only copy from
the PDC. Win2k DCs are all writable.

That being clarified, Are all machines pointing only to the DC with DNS and
no other, in their TCP/IP properties?
Are these two DCs in the same subnet? same location?
if you run nslookup on the machine you call the BDC for the name of the PDC
does it resolve?
What OS are the problem clients?
It might help to see an ipconfig /all from both DCs

 

[Kris Sokolowski]

Thanks for the advice... The answer to all of your questions is yes, and
the clients are running W2K. I had another look at the problem and was able
to see that it was the machine called BDC that was unable to see anything on
the machine called PDC. I requested a reboot of machine BDC and lo and
behold the problem has disappeared, (guess I should have rebooted both
machines and had a look then).