Netgear DG814 problems.

[johnboy]

Hi everyone.

I've just migrated to IDnet from Nildram and the migration was due last Thursday. As I didn't hear anything and I was still connected to Nildram I didn't do anything until Friday when I contacted IDnet support. They confirmed that th migration had completed and I just had to change my settings to transfer to IDnet. That's when the problem started.

As soon as I changed the DG814 settings I lost and couldn't reconnect to the internet. After trying all day to find out what could be wrong I contacted support again and they confirmed that the line was active (I was getting a light up on the router when I reset it) and the problem was between my computer and router. Eventually I gave up and was going to contact Netgear asap but my son-in-law came around with his router (DG834G). He checked the settings on the DG814 and they all seemed okay but every time the test key was pressed we lost connection to the internet. He then unplugged the DG814, plugged up the DG834G, applied the settings pressed test and bingo it connected first time.

Does anyone have any idea why the DG814 won't connect to IDnet when the DG834G connects easily. Incidentally I was on virtually the same package with Nildram as I am with IDnet and the router worked fine on Nildram.

I've bought a DG834PN this morning so it's just out of interest that I'd like to know what the problem might be with the DG814.

[Jeff]

johnboy, welcome to the IDNetters man I`m sorry nobody has took the time to offer any help ... I think they`re all pinging telehouse but as over 30 hours has passed since your plea for help, I`m hoping that things have transpired to the positive. Please come back if not

[johnboy]

Thanks Jeff

It's not a problem any more as I've got a new router as per my post but I just wondered why the DG814 wouldn't connect to IDnet.  The only differences I could see were that IDnet uses CHAP authentication and there's no mention of that on the DG814 settings page also IDnet gave me a static IP address which I haven't had before. I'm not up on the technical side enough to know if either of these would make any difference to the router being able to connect or not.

John

[cavillas]

Slightly, but not completely related.  I have a USRobotics 9016 router.  When I tried to set it up with the supplied software (to IDNet) it would not configure but had been alroght with my ote ISP.  I then went into the routers web page setup and had no problem setting it up with the same settings as the software.  Wondered if it was a similar problem with your router.

[johnboy]

I don't think so as I was using the router settings page all along. I had an internet connected light on the router but when I confirmed the settings and pressed the test button it just dropped the internet connection.

When my son in law checked the event viewer he noticed some errors relating to DHCPNACK but I'm afraid neither of us know what this refers to.

Thanks for your reply.

John

[equk]

When my son in law checked the event viewer he noticed some errors relating to DHCPNACK but I'm afraid neither of us know what this refers to.

Thanks for your reply.

John

Sounds like the host was denying the DHCP request from the router, or something along those lines  . Most certainly DHCP related.

Did you try setting a fixed IP rather than making it use DHCP 

DHCPAck and DHCPNack
When the DHCP server receives the DHCPRequest, it compares the network id of client's previously allocated IP address to the network id of the Relay IP Address.

If the two network ids are the same and the IP address can be reallocated to the DHCP client, the DHCP server initially sends a DHCPAck to the IP address found in the Relay IP Address field. When the DHCP Relay Agent receives the DHCPAck, it re-addresses it to the client's offered IP address and MAC address.
If the two network ids are the same and the IP address cannot be reallocated to the DHCP client, the DHCP server initially sends a DHCPNack to the IP address found in the Relay IP Address field. When the DHCP Relay Agent receives the DHCPNack, it re-addresses it to the client's offered IP address and MAC address. At this point, the DHCP client must restart the IP address allocation process with a DHCPDiscover.
If the two network ids are not the same, the DHCP client has moved to a different subnet, and the DHCP server sends a DHCPNack to the IP address found in the Relay IP Address field. When the DHCP Relay Agent receives the DHCPNack, it re-addresses it to the client's offered IP address and MAC address. At this point, the DHCP client must restart the IP address allocation process with a DHCPDiscover.

I have a DG814 but it kept disconnecting every hour or so, so I gave it to my office to use as they never notice the disconnects.

Still sounds strange that it suddenly works with another router

[johnboy]

Sounds like the host was denying the DHCP request from the router, or something along those lines  . Most certainly DHCP related.

Did you try setting a fixed IP rather than making it use DHCP 

We set the fixed IP address that IDnet supplied. My previous ISPs haven't supplied fixed addresses and the router was working with Nildram the day I changed to the IDnet settings.

I know that the DG814 doesn't have all the bells and whistles that the newer models have but I still can't understand why it wouldn't connect to IDnet after being connected to Nildram just a short while before.

Anyway I'm up and running with the new router now so not to worry.

John

[Jeff]

johnboy, I don`t understand this neither ... there are users who have this exact hardware, I`m sure ... I`ll dig `em up or perhaps they can jump in. :\

Still, all`s well that ends well, eh?