Really need someone to help me, I'm at my wits end I tell you!!

blastman

blastman

blastman

Associate
Joined
8 Mar 2007
Posts
2,176
Location
between here and there
Hi all,

I have a odd issue that I'm (an it professional) unable to fix.

you've heard what they sat about a plumbers taps always leak, well in a nut shell, I can't get any LAN connections to work at home.

This is my setup. I've reduced the amount of connected kit to try and work out whats happening and why;

PC (HTPC) running win7
PC (web server) ruuning fedora 16
PC (new HTPC) running ubuntu 12.4
laptop (MBPr) running osx (wifi)
appple tv2 (wifi)
xbox 360 (wifi)


as you can see, I've only got a couple of LAN devices in use. I do have loads of others but they're all disabled for the time being.

I've had to move everything to wifi as the LAN connections don't work.

I've tried every port on the router, I've tried 3 different routers (2 of them new!) I've used both dhcp and static addresses which is where it get even more strange...

If I set a static ip on the fedora box, it works, I can ping the router and get onto the internet, BUT only if i give it an address above .100??!???

the dhcp service on the router is set to scope from .2 to .254.

I've factory reset my router a biljilion times and sometimes, it'll work (lan device get an ip and can see the web) but as soon as i change any config, boom all stop again.

i'm at my wits end.

i can't find the common item thats causes these issues.

What i'm looking a for here is some other things i can test/try to try and pin down the cause.

any ideas/comments welcome.

thanks.
 
What router is it?

I would factory reset and then narrow down absolutely everything you don't need e.g. work with just the Windows 7 machine, plug it in to the router after the factory reset and check if it is assigned an IP by DHCP.

Have you checked to see if there are any firmware updates available for the router? I would probably do that before / instead of a factory reset and then work from there.

If it does succeed in assigning an IP then begin your configuration. Don't change everything at once, do it incrementally so if something does mess it up you should be able to pin point exactly what it was. Once you have a working config you should be able to export that as a backup for later.

After that you can start introducing your remaining devices.
 
netgear dgn2000.

I've done exactly that, expect I'm using the ubuntu machine as the testing rig.

I've done the 5th reset today and I've got an active connection on the ubuntu machine now.

I have been adding things and config one at a time, but hadn't considered backing up the config when a test is successful.

I'll do that now.

What bothers me, is it's not just the netgear router. I've also got a cisco and TP link (netgear with different badge) and they all act the same. This makes me think there is something on my network causing the dhcp requests to time out. But with nothing else attached or plugged in I'm at a complete loss!!

I'll post back shortly with updates.... fun fun fun. :(
 
So for testing are you connecting your machine directly to the router?

If multiple routers react in the same way then I'm assuming the common items between the tests would be the wiring and the machine itself.

You could try the same router, and an alternative, with different wiring, connected directly to an alternative machine (and only that machine). I would perform that test on a fresh config (either factory reset or fresh firmware).

If you get the same results from that then that is very puzzling.
 
Listen. Remove all your devices. Reset the router. Give the scope on the router .50 to .254 but only use static addresses (.1 been the router to .49)

1 at a time add them back. DHCP addresses are only used for devices like printers / servers.

For problems like this and been in IT you really should be able to solve them. IF things still fail it has to be the routers that are giving addresses out.
 
Mr. Peri Peri said:
So for testing are you connecting your machine directly to the router?

If multiple routers react in the same way then I'm assuming the common items between the tests would be the wiring and the machine itself.

You could try the same router, and an alternative, with different wiring, connected directly to an alternative machine (and only that machine). I would perform that test on a fresh config (either factory reset or fresh firmware).

If you get the same results from that then that is very puzzling.
Click to expand...

yes. cat6 from pc to router. tried all ports, same results. tried both pan cards I can, same results.

I'll try that now.

Yes my dgn2000 does start with that serial.... why do you ask?

So far I've managed to work out that i can reset the router and get a connection. I can upgrade the firmware and it still works. I changed the admin password and it still works. I rebooted the ubuntu machine and it dropped out and failed to reconnect on startup.
 
Having looked online there seems to be no end of problems with this Netgear router, particularly with the wired ethernet ports and blown capacitors, overheating issues, and problems with DHCP, and as stated above there's a particular LAN issue with models beginning with that serial number.

I think you could be on a high road to nothing with this router and so I would try testing with the Cisco instead. I know you said they all seem to be doing the same thing but it could be a separate issue with similar symptoms causing confusion.

How old is the Netgear? I believe you have a 2 year warranty on them in the UK so if still within that you could look at getting a replacement.
 
right....

I think I might have nailed it.

Yes I'm willing to accept that the netgear router has 'issues'. The router it's self was given to me 3 or so years ago, just as that model was released, by a staff member at netgear.

I have had loads of bits off him in the past so I'm not worried about fixing the dgn. I'm still waiting for him to hand me a new NAS.....

Turns out, the cisco router had the dhcp server disabled on it which is why the results looked the same.

ie, no network connections to devices.

the TP link router wouldn't connect to BskyB no matter what i did, so I've binned that off too.

Currently the cisco is working ok, will 2 wifi devices working and the ubuntu PC, which now has 130 updates to do..

Just about to turn the atv2 and xbox on to see they now work over cat5 when they used to only work on wifi...

bear with..... bear with...... bear with......
 
BOOM!!!

We. Are. Back .In .Business!!!


woop woop!!

it's only been 6 months.... :)

can't thank you all enough. There wasn't really any new information provided, but sometimes you simply need a sound board to vent at. You all did very well!

thanks again,

:)
 
mrbell1984 said:
Hold on..... so you never bothered purchasing a new one in the first place? and it was the router?
Click to expand...

why would i want to buy a new one when i had another 2 new routers that i had yet to use?

I suspected the router at first, but when i tried the cisco and got the same type of error's i thought it to be machine related. after i found that didn't work i came here.

I asked for some advice and help, not sarcastic comments.
 
mrbell1984 said:
Listen. Remove all your devices. Reset the router. Give the scope on the router .50 to .254 but only use static addresses (.1 been the router to .49)

1 at a time add them back. DHCP addresses are only used for devices like printers / servers.

For problems like this and been in IT you really should be able to solve them. IF things still fail it has to be the routers that are giving addresses out.
Click to expand...

Statics for servers and printers mate, not DHCP.
 
You must log in or register to reply here.
Back
Top Bottom