Question for a future event.

Joi · 02-26-2007, 10:08 AM

I want to ask this question in the event I ever run into it again.
I had an XP box on my network and it would not connect to the Internet. I performed an ipconfig /all and noticed that the default gateway that box was going to was 255.255.255.255. Right!?

I did not know why it wasn't going to my default gateway (router) correct address which is also the DHCP server. If it had then all the fields would had been populated correctly and route out.

I then manually entered the information, didn't work. So I googled for the problem and the only thing I found to do regarding the problem was select the connection > right click > repair connection. We'll I tried that and it didn't fix the problem.

So, what I ended up doing is just upgrading that box to Vista and it cleared out the problem.

Now. I'd like to know what to do in the event that ever happens again because my other boxes on my network are XP and I won't be able to upgrade them like that to Vista if it happens on these other boxes. I was lucky, I had the "option" for that particular box, but forget doing that on these other ones.

Any advice on why XP would goto 255.255.255.255 for the default gateway ip? Any suggestions on how to fix it "properly" next time?

rob1210 · 03-06-2007, 04:19 PM

Would be helpful that if you get the problem again on another machine to post the IPCONFIG /ALL results first. The 255.255.255.255 is a subnet address? Lord only knows why it would give you that as a gateway address? An important thing to look at would be to ensure firstly that you are getting a correct IP address from the DHCP device.

Oogitsmelol · 03-06-2007, 04:45 PM

i would hope it wouldnt give that to you as a subnet address either. it wouldnt work if it did... i guess if it does it again you can always tell your router to use static routes and set everything up yourself...

johnwill · 03-06-2007, 06:29 PM

Actually, the subnet address 255.255.255.255 is valid, it's for a subnet of one.

From: http://support.microsoft.com/kb/140859

Quote:

The Netmask defines what portion of the Network Address must match for that route to be used. When the mask is written in binary a 1 is significant (must match) and a 0 need not match. For example, a 255.255.255.255 mask is used for a host entry. The mask of all 255s (all 1s) means that the destination address of the packet to be routed must exactly match the Network Address for this route to be used.

rob1210 · 03-07-2007, 01:33 AM

Quote:

Originally Posted by johnwill

Actually, the subnet address 255.255.255.255 is valid, it's for a subnet of one.

From: http://support.microsoft.com/kb/140859

John, I am aware that 255.255.255.255 is a valid subnet address but the original question stated that they were getting that as a gateway address?

johnwill · 03-07-2007, 07:35 AM

Quote:

Originally Posted by rob1210

John, I am aware that 255.255.255.255 is a valid subnet address but the original question stated that they were getting that as a gateway address?

Well, I'm just responding to your post.

Quote:

The 255.255.255.255 is a subnet address?

I'd find it curious as a gateway address. Usually, when you start getting oddball results like that, something is wrong at the driver or hardware level.

rob1210 · 03-07-2007, 07:40 AM

indeed, think the best bet would be to see the ipconfig when and if you get this issue again then we can all make an educated guess

02-26-2007, 10:08 AM	#1 (permalink)
Joi Registered User Join Date: Feb 2007 Posts: 5 OS: WinXP	Question for a future event. I want to ask this question in the event I ever run into it again. I had an XP box on my network and it would not connect to the Internet. I performed an ipconfig /all and noticed that the default gateway that box was going to was 255.255.255.255. Right!? I did not know why it wasn't going to my default gateway (router) correct address which is also the DHCP server. If it had then all the fields would had been populated correctly and route out. I then manually entered the information, didn't work. So I googled for the problem and the only thing I found to do regarding the problem was select the connection > right click > repair connection. We'll I tried that and it didn't fix the problem. So, what I ended up doing is just upgrading that box to Vista and it cleared out the problem. Now. I'd like to know what to do in the event that ever happens again because my other boxes on my network are XP and I won't be able to upgrade them like that to Vista if it happens on these other boxes. I was lucky, I had the "option" for that particular box, but forget doing that on these other ones. Any advice on why XP would goto 255.255.255.255 for the default gateway ip? Any suggestions on how to fix it "properly" next time?

03-06-2007, 04:19 PM	#2 (permalink)
rob1210 Registered User Join Date: Mar 2007 Location: UK Posts: 13 OS: XP/Vista	Would be helpful that if you get the problem again on another machine to post the IPCONFIG /ALL results first. The 255.255.255.255 is a subnet address? Lord only knows why it would give you that as a gateway address? An important thing to look at would be to ensure firstly that you are getting a correct IP address from the DHCP device. __________________ IF THINGS DONT CHANGE THEY'LL STAY AS THEY ARE

03-07-2007, 07:40 AM	#7 (permalink)
rob1210 Registered User Join Date: Mar 2007 Location: UK Posts: 13 OS: XP/Vista	indeed, think the best bet would be to see the ipconfig when and if you get this issue again then we can all make an educated guess __________________ IF THINGS DONT CHANGE THEY'LL STAY AS THEY ARE

03-06-2007, 04:45 PM	#3 (permalink)
Oogitsmelol Registered User Join Date: Mar 2007 Posts: 51 OS: Windows XP	i would hope it wouldnt give that to you as a subnet address either. it wouldnt work if it did... i guess if it does it again you can always tell your router to use static routes and set everything up yourself...