Author Topic: Cant access PC by hostname until after I ping it (Read 1323 times)

addictweb · **on:** October 08, 2011, 14:26:06 PM

Cant access PC by hostname until after I ping it

on: October 08, 2011, 14:26:06 PM

I've recently had a reshuffle of my equipment and my HTPC and NAS box now sit behind (separate) switches.

From any PC on the network I cant access \\htpc or \\nas or any service they are hosting until after I ping their IP address.

I assume I have a DNS issue somewhere but I cant workout where, and to be honest I'm not really sure what I'm looking for. The switches are both routers with their DHCP turned off.

Any pointers?

XEntity · **Reply #1 on:** October 08, 2011, 16:19:29 PM

Re: Cant access PC by hostname until after I ping it

Reply #1 on: October 08, 2011, 16:19:29 PM

Sounds interesting, but I believe this is netbios not DNS on the LAN? And does sound like a routing issue, maybe try a google using netbios in the search..

I'm not sure I can help much more than that, double check the IP and subnets setup on the routers?

I assume the routers have static IPs? and not assigning via DHCP?

Russell · **Reply #2 on:** October 08, 2011, 20:52:19 PM

Re: Cant access PC by hostname until after I ping it

Reply #2 on: October 08, 2011, 20:52:19 PM

Not sure exactly but it will probably be down to having the DHCP turned off, assuming that the built in DHCP works similarly to DHCP/DNS on a windows domain then when you get a DHCP address it automatically registeres your DNS entry for you and since your DHCP is turned off on both routers it'll never register DNS and ergo no name resolution. I presume that when you ping by IP address it adds it to its internal routing tables and you can then ping by name.

Probably the easiest way to get this working right is to turn on one of the routers DHCP servers, I can't think of any reason why it won't let you but if it doesn't then buy yourself a cheapo hub/switch and use that instead of the 2nd router.

News: