name resolution???

[reds17]

I have multiple Windows 2000 member servers in a Windows
Server 2003 domain. On one of the Servers I'm having
intermittent success and failure when trying to connect
via a UNC path or Computer Management. DNS is not an
issue, I can resolve the IP through the ping command
using both the physical IP address and the computername.
We also are not using WINS on our network in spite of the
fact that the majority of our system have NetBIOS over
TCP/IP enabled. I've tried:
1. Disabling NetBIOS on the adapter
2. Removing and reinstalling all network components
3. Renaming the Server
4. Removing from the domain, deleting all DNS and
computer object entries, then re-adding to the domain.

Nothing works!!!! Any suggestions.

 

[Doug Sherman [MVP]]

You should be able to connect through Computer Management and UNC paths with
an IP address instead of a computer name.

Eg.: \\192.168.1.1\sharename.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

 

[Guest]

-----Original Message-----
You should be able to connect through Computer Management and UNC paths with
an IP address instead of a computer name.

Eg.: \\192.168.1.1\sharename.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP




.
Yeah, tried that too. I did find out the problem after

all this. Turns out it was another device on the network
using the same IP!!! I never received any indication
through any IP conflict messages but that's what it was.
It's in a static address range put aside for all of our
Servers and some other misc. devices. Thanks anyhow.