We use cookies to provide you with a better experience. If you continue to use this site, we'll assume you're happy with this. Alternatively, click here to find out how to manage these cookies

hide cookie message
Contact Forum Editor

Send an email to our Forum Editor:


PLEASE NOTE: Your name is used only to let the Forum Editor know who sent the message. Both your name and email address will not be used for any other purpose.

Tech Helproom


It's free to register, to post a question or to start / join a discussion


 

DHCP not working for wired LAN


Batch
Resolved

Likes # 0

I have a relatively new laptop running Win7 HP x64.

I have two brands of router. A Thompson TG585v7 - everything works fine on that.

On the other router (a 3Com 3CRWDR101A-75 which I prefer and so tend to use), the wireless adapter connects to the router OK using DHCP and picks up its IP address fine.

But the wired adapter doesn't seem to pick up the IP address and so appears to use a fixed default (presumably supplied by RealTek - the adapter manufacturer). Not unreasonably, the router objects to this IP address as it is not in an acceptable / known range (treats packets as SMURFs). I assume it can't be the settings on the lappie as it works fine with the other router (and anyhow I've checked the settings to ensure that it is set to obtain IP address automatically).

By way of contrast, on my 3 other computers (desktop, lappie, netbook all on XP SP3) wired and wireless all work fine with either router.

Any ideas?

Like this post
Batch

Likes # 0

Problem solved (after a fashion).

One of the reasons I prefer the 3com router is that it is very flexible and provides reasonably detailed logs.

On the 3com router I had set-up the local network IP range to be in the 172.27.xxx.xxx block (perfectly legit - see http://en.wikipedia.org/wiki/Private_network). This has always worked fine before.

On the Thomson (as supplied in a pre-set and locked state by my ISP) one cannot change the local net range and so are stuck with 192.168.xxx.xxx

Changing the 3com router to be in the 192.168.xxx.xxx seems to have overcome the issue.

Like this post
Batch

Likes # 0

Link again

http://en.wikipedia.org/wiki/Private_network

One of these days PCA will get it right!

Like this post
Batch

Likes # 0

Thought about this some more and it just didn't seem right. Although changing the IP address range used by the router for DHCP seemed to overcome this issue, I wasn't happy with the rationale as to why it had happened.

Having slept on it I wondered if it might be to do with me Leaving The HomeGroup and Disabling HomeGroup - whilst the wired network adapter wasn't in use (but the WiFi adapter was in use).

I did a restore and tried again with both adapters active and it all worked fine this time. It seems that leaving and/or disabling the HomeGroup when an adapter is not active leaves that adapter somehow still tied to that HomeGroup and unable to connect properly. Windows then uses the 169.254.0.0-169.254.255.255 as per:-

"If a DHCP server does not respond after several discover messages are broadcast, the Windows computer assigns itself a Class B (APIPA) address. The Internet Assigned Numbers Authority (IANA) has reserved 169.254.0.0-169.254.255.255 for Automatic Private IP Addressing. As a result, APIPA provides an address that is guaranteed not to conflict with routable addresses."

So now I know.

Like this post  

Reply to this topic

This thread has been locked.



IDG UK Sites

Best Christmas 2014 UK tech deals, Boxing Day 2014 UK tech deals & January sales 2015 UK tech...

IDG UK Sites

Chromebooks: ready for the prime time (but not for everybody)

IDG UK Sites

Hands-on with Sony's latest smartglasses

IDG UK Sites

Apple TV setup advice: Apple TV hacks to help you create the ultimate Apple TV hub in your home