neilaubin
join:2004-12-04
UK | reply to Big Hoot
Re: Netgear DG834G intermittent timeout/connectivity
Well, due to the lack of help here then I logged a call with Netgear and went through everything I had done. They are now going to replace the router and I will see how I get on with the new one.
Neil |
|
Archibold
| Re: Netgear DG834G intermittent timeout/connectivi
I've seen the same symptoms. I've isolated them to the DNS-implementation in the router.
The DG834G acts as some kind of DNS-proxy. It gets the DNS-settings by DHCP from my ISP. But it does not forward these addresses to my clients using DHCP. Instead, it provides it's own address.
The solution for me has been to use static DNS-configuration on my clients.
If I'm correct, a new unit won't solve this issue. Netgear can fix it in the firmware though. One simple solution would be to make the DHCP/DNS-settings configurable. I'd rather have the router pass along the actual DNS-entries. |
|
neilaubin
join:2004-12-04
UK | Thanks for this. Can I ask for a full explanation of what you have therefore configured on the router and what you have done on the client. I think I understand but I want to make sure.
Thanks again. |
|
Archibold
| neilaubin,
Sure. First, check the DNS-settings on the router. Just go to the "Router status" page in the administrative interface (»192.168.0.1/setup.cgi?next_file=start.htm).
Write down the addresses for "Domain Name Server" in the first section.
Use the addresses when configuring TCP/IP for your clients interfaces. I use Mac and it's quite straightforward. I think it's just as simple on Windows. Just choose the network-interface, modify the TCP/IP-settings and enter the DNS-addresses.
You can ealisy check that the DNS-implementation is flaky by using nslookup. Try switching back and forth between the router and the actual DNS. After a couple of simple queries you'll see that the router is somewhat random in it's responses.
I'll check out WillBristows tips as well. I've seen that my ADSL-line drops connection every now and then and never been able to figure out why. This is a separate issue from the DNS-thing though. |
|
