Can't work with IP, but can with names

[frki80]

Hi,
I work with SBS2003, and there is problem with IP address.
I can ping clients from server either with IP or hostname. But when I try to connect to any client, I can connect only with hostname (\\PC1\), but I can't connect with ip address (\\192.168.1.6\).
Any idea?

p.s.
I check relation between IP address and hostname with nslookup, and thats OK.

 

[Molenski]

It isn't some sort of firewall issue is it?

 

[frki80]

There is no firewall, or antivirus.

 

[Molenski]

What's the error message? Anything in the Event logs on the local machine. Can you map from client to server using IP?

 

[frki80]

Error message:
"Windows cannot find '\\192.168.1.6'. Check the spelling and try again, or try searching for the item by clicking Start button and than clicking Search."

Yes. I can map from client to server using IP, but I can't map from server to client using IP, only by names.

 

[Molenski]

The IP address you have is definately correct for the client? Have you tried putting a sniffer on the network to check out any errors?

 

[frki80]

nslookup say that ip 192.168.0.6 is for client "office". I try packet sniffer but there is no traffic after server...

 

[Molenski]

So the client is called office? You said earlier the address was 1.6 and not 0.6? If you logon to the client and run an ipconfig, the IP address is 192.168.0.6 or 1.6?

 

[frki80]

Typing error, client is 1.6

 

[Molenski]

...and that is confirmed locally on the client...?

 

[frki80]

Yes! With ipconfig/all on client host.

 

[Molenski]

Mmmm...no intermediatery networking devices? How about from the command prompt:

net use \\ipaddress\sharename

 

[NEmacGuy]

Reverse DNS issue ? Does your SBS server have a x.1.168.192 zone

 

[frki80]

What I need to change? There is 192.168.1.x reverse dns.

 

[muckermucker]

You do know that a reverse lookup zone doesn't always match the forward lookup zone right?? so when you are testing this there could be stale records.
They are different zones therefore differnt tables/data.

Your forward lookup zone will resolve the name "office" to an IP.
But your revers lookup zone may not have been updated in ages so when you quesry this zone it may match an old IP.

I think you may be doing the following:

Connecting by name and it works but you haven't pinged it by name to see what THE FORWARD lookup zone resolves to. This IP may be 192.168.1.89 for example.
Instead you used NSlookup and did a reverse lookup. This queries the reversre lookup zone giving a stale record of 192.168.1.6.

You then assume that this is IP and try to connect to it via a windows share when in fact this is not the IP.

Try looking in your forward lookp zone to see what IP the "Office" name resolves to. It might be different. This scenario above would give these exact symptons you are experiencing and is easily overlooked. I only know about it as it had me stumped for ages once!

Take a look at my IT blog guides, knowledgebase and technical resources at

http://think-like-a-computer.com