A
aaron
I think this is more of a WINS problem but here goes. I have one machine on
the network that is periodically getting a "duplicate name exists blah,blah"
error. The machine name is very unique, the MAC is unique. When the user
gets this message and nbtstat -a "computer name" returns one of our jet
direct printers, If I continue to refresh the nbtstat command it will
eventually give me a different network printer name. I have checked all WINS
and DNS records, to see if there was a duplicate record. I have made sure
the printers did not have the same name anywhere in the config. I am at a
loss on this one.
Ping results in the correct machine name and IP
nslookup results in the correct machine name
nbtstat results in wrong name.
XP Pro workstation SP1
TCP/IP network
Printers running DLC and TCP/IP protocols.
Any suggestions?
TIA,
aaron
the network that is periodically getting a "duplicate name exists blah,blah"
error. The machine name is very unique, the MAC is unique. When the user
gets this message and nbtstat -a "computer name" returns one of our jet
direct printers, If I continue to refresh the nbtstat command it will
eventually give me a different network printer name. I have checked all WINS
and DNS records, to see if there was a duplicate record. I have made sure
the printers did not have the same name anywhere in the config. I am at a
loss on this one.
Ping results in the correct machine name and IP
nslookup results in the correct machine name
nbtstat results in wrong name.
XP Pro workstation SP1
TCP/IP network
Printers running DLC and TCP/IP protocols.
Any suggestions?
TIA,
aaron