Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dg]

Just upgraded to DIR825revB from very old G-router which was working fine but had limited range and a cracked antenna. Unfortunately, altho the D-Link works, it frequently disconnects requiring either a reboot of the DSL modem or the router or both.  If I switch the cables back to the old router everything works fine.  When I switch them back to the DIR-825, it works for 5 -25 minutes, then disconnects again. 

Set it up manually, but checked all settings with Tech Support already b/c of earlier problem connecting at all which seemed to be resolved.  Upgraded to FW 2.05 on tech support's advice. Have Verizon DSL (thinking of switching to cable) with Westell InfoSpeed B90 modem.  Using WPA.  Have 1 wired Win7 desktop, 1 WinXP either wired or wireless, 1 Mac OSX wired or wireless, and several more Macs.  Also a 2.4GHz cordless phone (which is why I got this dual mode router).  QoS and AdvDNS are off.  When I try diagnostics on the clients, sometimes I get: "DNS Server isn't responding".  I've tried setting the DNS to 4.2.2.2 / 4.2.2.3 or leaving them out to use Verizon's DNS, but that doesn't seem to affect anything. 

I'm back to the old router for now.  Would greatly appreciate any suggestions. Thx.  :Dani

[FurryNutz]

What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.

Ensure DNS IP addresses are being filled in under Setup/Internet/Manual?
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices on the router.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP.

What wireless modes are you using?
Try single mode G or mixed G and N on 2.4Ghz and single mode N on 5Ghz.
Preferred is WPA Personal. Auto TPIK and AES.
Cordless phones in the house can cause the router to drop wireless.
Any other WiFi routers in the area?

Turn off all anti virus and firewall programs on PC while testing.
Turn off all devices accept for one wired PC while testing.

[SirMaggot]

try to disable "DNS Relay"
->Setup -> Network settings

[dg]

Thanks greatly for these suggestions.  It will take a bit of time to try them, but I will over the next day or so.

What ISP Modem do you have? Stand Alone or built in router? Verizon Westel B90 without router built in.

Ensure DNS IP addresses are being filled in under Setup/Internet/Manual?   They are.
Turn on DNS Relay under Setup/Networking.  It is.  But what is this?  Other poster suggested disabling it.  
Setup DHCP reserved IP addresses for all devices on the router.    OK.  Am trying that.
Ensure devices are set to auto obtain an IP address.    They are.  Set Firewall settings to Endpoint Independent for TCP and UDP. Will try that next (to try to test one change at a time.) They are now at UDP Address-restricted and TCP Port & Address-Restricted.  What exactly do these mean?

What wireless modes are you using? Both N & G; 2.4 & 5GHz.  

Try single mode G or mixed G and N on 2.4Ghz and single mode N on 5Ghz.   OK.  Will try that too.  
Preferred is WPA Personal. Auto TPIK and AES. That's what it is.
Cordless phones in the house can cause the router to drop wireless.   That's one of the reasons we got the dual band router.  But I did unplug the cordless and still had the same problem.  Also had it on 5GHz but we don't have any other 5GHz devices.
Any other WiFi routers in the area? Ahh.  As we're in a New York City apartment building, there are lots of other WiFi routers within detection range, but none nearly as strong and close as our router and the laptops using it from the same room.  

Turn off all anti virus and firewall programs on PC while testing. Will do this last, altho it makes me nervous.  I'm using Windows firewall and MS Security Essentials on the wired Win7 & Windows Firewall & Avira on the wireless WinXP and no AV on the Mac OSX's and whatever firewall they come with  - not even sure what that is.
Turn off all devices accept for one wired PC while testing.   This i've tried, but to no avail.

 Thx.  :Dani

[SirMaggot]

Try this one first.
Try single mode G or N on 2.4Ghz and single mode N on 5Ghz.

Info on DNS Relay
When DNS Relay is enabled, the router plays the role of a DNS server. DNS requests sent to the router are forwarded to the ISP's DNS server. This provides a constant DNS address that LAN computers can use, even when the router obtains a different DNS server address from the ISP upon re-establishing the WAN connection. You should disable DNS relay if you implement a LAN-side DNS server as a virtual server.

[FurryNutz]

Thanks greatly for these suggestions.  It will take a bit of time to try them, but I will over the next day or so.
  Thx.  :Dani

Turn on DNS Relay under Setup/Networking.  It is.  But what is this?  Other poster suggested disabling it. What Sir Maggot said.  I recommend leaving this ON for now. Since the router is handling all of the traffic, and your devices are set up for auto. This will ensure DNS is getting to and from the devices.

Set Firewall settings to Endpoint Independent for TCP and UDP.  Will try that next (to try to test one change at a time.) They are now at UDP Address-restricted and TCP Port & Address-Restricted.  What exactly do these mean?
NAT Endpoint Filtering

The NAT Endpoint Filtering options control how the router's NAT manages incoming connection requests to ports that are already being used.
Endpoint Independent
Once a LAN-side application has created a connection through a specific port, the NAT will forward any incoming connection requests with the same port to the LAN-side application regardless of their origin. This is the least restrictive option, giving the best connectivity and allowing some applications (P2P applications in particular) to behave almost as if they are directly connected to the Internet.
Address Restricted
The NAT forwards incoming connection requests to a LAN-side host only when they come from the same IP address with which a connection was established. This allows the remote application to send data back through a port different from the one used when the outgoing session was created.
Port And Address Restricted
The NAT does not forward any incoming connection requests with the same port address as an already establish connection.

Note that some of these options can interact with other port restrictions. Endpoint Independent Filtering takes priority over inbound filters or schedules, so it is possible for an incoming session request related to an outgoing session to enter through a port in spite of an active inbound filter on that port. However, packets will be rejected as expected when sent to blocked ports (whether blocked by schedule or by inbound filter) for which there are no active sessions. Port and Address Restricted Filtering ensures that inbound filters and schedules work precisely, but prevents some level of connectivity, and therefore might require the use of port triggers, virtual servers, or port forwarding to open the ports needed by the application. Address Restricted Filtering gives a compromise position, which avoids problems when communicating with certain other types of NAT router (symmetric NATs in particular) but leaves inbound filters and scheduled access working as expected.
UDP Endpoint Filtering
Controls endpoint filtering for packets of the UDP protocol.
TCP Endpoint Filtering
Controls endpoint filtering for packets of the TCP protocol.

Formerly, the terms "Full Cone", "Restricted Cone", "Port Restricted Cone" and "Symmetric" were used to refer to different variations of NATs. These terms are purposely not used here, because they do not fully describe the behavior of this router's NAT. While not a perfect mapping, the following loose correspondences between the "cone" classification and the "endpoint filtering" modes can be drawn if this router is configured for endpoint independent filtering, it implements full cone behavior; address restricted filtering implements restricted cone behavior; and port and address restricted filtering implements port restricted cone behavior.

Any other WiFi routers in the area?  Ahh.  As we're in a New York City apartment building, there are lots of other WiFi routers within detection range, but none nearly as strong and close as our router and the laptops using it from the same room.  I see, knowing this, this also could be a reason why the router is disconnecting sometimes, specially on WiFi. Having a lot of other routers near by can have an effect on this along with cordless phones. I hope that SirMaggots suggestion of going single mode on each radio might help narrow down the issue some. I recommend using InSSIDer application to see what other routers are using for channels. Might be one you can use if there is one open. I might also suggest that you lower the power out put of the WiFi. Since everyone is maxed out of the box, and then being a small apt or faily small apt. The routers radio out put doesn't need to be at full power since your only in a small area, theres no need to broadcast over a long distant. Lower the power some and test and see if this also helps.

Keep us posted. Might have someone here use teamviewer.com and help you check your router settings. It's free and safe to use.