Desktop PC is connected to the net but isnīt?

[Saab Dastard]

bnt,

It is clear that the gateway address is 10.0.0.138, and the PC IP address is 10.0.0.1.

Unusual, but hey, there's nothing wrong with it.

DHCP is already set for the PC - but it appears that it isn't working for DNS server settings, for whatever reason, as it is assigning the gateway address as the DNS server.

There's nothing peculiar about the fact that the Mac is working. It obviously has valid DNS settings.

The "destination can not be reached" is the response you expect with the default gateway being configured as the DNS server - but you are right to say that the PC must therefore be talking to the gateway.

Restarting the router and then running "ipconfig /release" and "ipconfig /renew" might help to reset the DNS config.

I have had this problem before - and resorted to fixed IP addresses and manual DNS configuration. It is a LOT more reliable! And technically a little bit more secure!

SD

[bnt]

Both of you with the snarky comments: yes, I spotted my mistakes, and was fixing them as you were typing. Try again?

Normally the router is at one end of the range, ...1 or ...254. Having it on ...138 is just weird. Having the router as the DNS server is not wrong, that's what I have here: the router is a DNS relay.

Ethernet adapter Local Area Connection:
...
IP Address. . . . . . . . . . . . : 192.168.1.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : 11 March 2008 22:03:26
Lease Expires . . . . . . . . . . : 11 March 2008 23:03:26

[green granite]

my config is the same as Judd's xxx66 being the pc and xxx254 being the router and my system works fine.

Windows IP Configuration

Host Name . . . . . . . . . . . . : home-4e88e39f51
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-1D-60-3A-50-D4
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.66
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
Lease Obtained. . . . . . . . . . : 11 March 2008 10:29:05
Lease Expires . . . . . . . . . . : 12 March 2008 10:29:05



Could it be that whoever used it last changed the selection in the TCP/IP properties from "obtain DNS server address automatically" to "use the following"?

Suggest you go to start- contoll pannel-network connections then right click on the wireless connection select properties select TCP/IP click advanced and check that the box that says "obtain DNS server address automatically" is checked.

[Keef]

Mine does much the same - uses the default gateway as the DNS server - I suppose the router is clever enough to cope with that. I don't use DHCP because there's a VPN into this machine and that needs a fixed IP address, but it looks like this:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-0B-6A-92-30-A6
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.8.110
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.8.1
DNS Servers . . . . . . . . . . . : 192.168.8.1

What does seem a tad odd to me is that this machine is 10.0.0.1 - somehow, I'd have expected .1 to be reserved. My daughter has a similar set of addresses, and her first machine is 10.0.0.4 - other machines work up from there.

Anyway, let's see how Juud makes out from this step. I'd have expected Auto DHCP to work just fine, but if it won't, then fixed IPs do have a certain stability to recommend them.

[Saab Dastard]

I have to admit that I didn't think about the router acting as a DNS relay or DNS proxy.

Having said that, if it isn't working (as seems apparent) then my recommendation would still be to configure a fixed IP address and DNS servers.

What make and model is the router? The router setup should confirm if DNS Relay is in use, although some devices with no DNS Relay option will default to DNS Proxy if DHCP is enabled but no DNS servers are configured in the scope.

The status page should indicate what DNS servers addresses it has received from the ISP.

Regarding the Default Gateway address - there is no requirement to assign the first or last IP address in a range for the DG, it is simply a convention. Yes, it is peculiar for the DG to have .138 as its address, and the PC to have .1, but it is technically perfectly sound.

Perhaps it is an opportunity to overhaul the IP addressing scheme on the Juud network?

SD

[Eric]

Hi Juud,

Not been here for a while so don't know if this has now been sorted, but I have just sorted a similar problem out.

I have Zonealarm firewall which on the firewall settings should be set to medium, and windows update KB951748 should be removed via "add or remove programs" in the control panel.

Don't know if this will solve your problem but it might give the bigger boys a clue...