how-to block ads
51.0 ... Routers/Gateways (all types)
1. Unplug power to your broadband modem.
2. Unplug power to your router.
3. Shut down your network computers.
4. Wait for about 20-30 seconds before turning the modem back on. This allows the broadband modem to resynchronize with the network.
5. Wait for another 20-30 seconds. When you see the lights become stable, and the DSL or Cable light indicates a proper connection, plug in the router. This allows the router to resynchronize with the broadband modem.
6. Wait for another 20-30 seconds. When you see the lights begin to flicker randomly (indicating network traffic), and a light indicating your WAN port is connected, turn on your network computers. This allows your computers to automatically receive a renewed or updated IP address assignment through DHCP.
A. If the trouble returns, consider locking your WAN port's speed. This setting is found on the Tools / Misc portion of the web configuration pages on many D-Link DI-5xx and DI-6xx routers.
B. If you have a DSL modem and the trouble returns or persists, consider putting your DSL modem into Bridge mode -- or, on the modem, choose the option to deliver your IP address to the computer. For an example, see /faq/11827.
C. If the trouble persists, consider the possibility that the cable between the router and broadband modem is defective.
Feedback received on this FAQ entry:
The router is designed to reboot in order to prevent a more serious lockup or corruption. It is a last-resort effort to keep your network online. This does not mean that the designers' intended for you to tolerate a frequently rebooting router. But it does mean that there may be multiple possible causes leading to different suggestions to fix it.
If you're not sure whether your router is rebooting, check /faq/12901 in the D-Link forum FAQ.
In determining the cause leading to router reboots, it is necessary to determine which conditions were present at the time or which changes were made prior to the beginning of the reboots.
Frequent causes of reboots for all routers, and suggestions:
•Maintaining several hundred simultaneous connections, beyond the router's capacity.
This is most frequently caused by P2P filesharing software, but it is also sometimes associated with running a public web server behind a residential router. Set the software to maintain fewer simultaneous connections. One specific frequent rebooting issue is with the DI-5xx and DI-6xx numbered routers is eMule with the KAD feature enabled. Suggestions: If the router only restarts during P2P traffic, configure your P2P client to limit the number of connections to a lower number. If you are using eMule with KAD, try turning off the KAD feature.
•Keeping the router in a warm place or an unventilated place.
The router should be in a room-temperature place, free from direct sunlight or the draft from heating vents. Suggestions: Some have found that standing the router on an end provides for improved airflow and reduced reboots.
•Poor or noisy power source.
The D-Link supplied power supply may be insufficient, either by design or defect. Or the power supply may be plugged into an under-powered or noisy circuit. Suggestions: Some have found positive results by replacing the included power supply with another that meets or somewhat exceeds the AMP rating on the label. You can eliminating line noise from florescent lights or electric fan motors by increasing the distance between the device and these appliances, and ensuring that they do not share the same surge protector or power strip.
Frequent causes of reboots for wireless routers and APs, and suggestions:
•Interference from non-wifi uses of the 2.4 GHz (802.11b and 802.11g) band, or the 5.8 GHz (802.11a) band.
Such equipment includes cordless phones, baby monitors, security systems, wireless cameras, radar, microwave oven, wireless speakers, audio/video extenders, and etcetera. Keep in mind that interference may be coming from use of these products in neighboring homes and businesses. Suggestions: Keep distance between wi-fi equipment and other radio equipment using the same frequencies.
•Interference from adjacent wi-fi users that are not properly sharing the channel.
If a neighboring wi-fi network is repeatedly interfering with your network, the high number of resulting errors and retransmissions may cause your router to reboot. If you are using a proprietary version of wi-fi (22 Mbps or 108 Mbps), turn off 4x mode or Super-G mode. Suggestions: If the problem persists, either set your channel selector to Auto or manually choose another channel. Try turning off features that enhance the network performance by using technologies not included in the 802.11a, b, or g specification.
Note -- you can expect these issues if you are in a very populated area and are using G-Only mode or SuperG with Static Turbo. For different reasons, these modes may not be recognized by other wireless networks and their transmissions are more likely to occur simultaneously with your own.
•Self-inflicted interference caused by signal leaks into the non-radio components of the router.
Unfortunately, it is not uncommon to find that a wireless AP or router is creating its own electrical noise, causing itself to reboot. A tell-tale sign of this problem is that the issue goes away when the Transmit Power setting is reduced to 50% or less. Another is sign is when the problem stops after repositioning the AP on its end -- so that the antenna signal transmits over the narrow end of the device, instead of the long end. It should be noted that, no matter what the radio equipment, its antenna should not touch or be immediately adjacent to any other metal object. However, in some of the above cases, poor installation was not a factor. Suggestions: Rotate the chassis of the router or AP, and reposition its antenna, so that the signals radiate over less of the device's surface (in other words, stand it on its side instead of its bottom). Leave 8 inches (20 cm) or more separation between the router or AP and any other metal chassis or platforms. Reduce the transmit power to the antenna to 50%, or purchase an antenna with a cord that allows you to move the antenna further away from the device.
THIS FAQ ANSWER APPLIES TO most residential routers, and include additional information about wireless routers and Access Points (APs). Not every detail will apply to every device. FAQs in other areas are invited to add this question to their FAQs, but please point and update this copy of the Answer so that it is kept up to date.
Feedback received on this FAQ entry:
•Your Windows computers that are connected to the LAN ports indicate "Network Cable Unplugged." If you are using another computer or network device, you will get an indication that the Link has been momentarily broken. (Note: Wireless clients may not detect the interruption.)
•If you are using a DI-5xx/6xx/7xx device that supports NATLIST.TXT (not all do), you can get the uptime by using your browser to retrieve http://192.168.0.1/NATLIST.TXT. Look for the line that says "curr time : 369360" and divide that number by 60. The result is the number of minutes since the last reboot or power up.
•The DI-5xx/6xx/7xx router's log has been reset. Over time, the router's log should grow if the router is not rebooting. The last page will have the oldest entries. If your log is shorter than the maximum, the last entry will be the time your router last restarted. (The maximum log size is 20 pages long on many D-Link routers.)
•The lights flash in a particular pattern that you can learn. Go to Tools / Misc. On that page, one item should be "Reboot." Click that button as you are carefully watching the lights on the router. You can use this method to learn the pattern of the lights when the router is rebooting.
For more information, see /faq/11915
To prepare: Download the firmware you wish to use from support.dlink.com. You may wish to download two or three different versions in case a particular version does not agree with your router.
To crash recover:
•Connect to the router with a LAN cable. Do not use a wireless connection for this task.
•Unplug the power from the router.
•Hold in the reset button and plug the power back in. Continue holding for 10 seconds and then release.
•Statically assign an IP address** to your computer in the IP subnet range 192.168.0.x where x is any number between 2 and 254. Your Subnet Mask should be 255.255.255.0. (Gateway and DNS settings may be left blank or set to 192.168.0.1).
•Open Internet Explorer and browse to 192.168.0.1. You should see the crash recovery page.
•Browse to the location of the firmware on your hard-drive and click the send button. After pressing the send button, wait up to a minute for the process to complete. During this time, your web browser may "time out" or you will notice that your network has disconnected. Although somewhat unsettling, this is normal as the router reprograms itself.
•After those few moments, the router will be ready with the new firmware. It will be at factory defaults:
Tip: Do a factory reset at this point. Hold in the reset button for 10 seconds and then release. Do not unplug the power during this time.
•Your router is now ready to configure.
Tip: Do not attempt to restore a previously-saved configuration as it may contain the source of the corruption that led to the crash of your router. Reconfigure your router through the menus.
Thanks goes to Talon88 who has steadfastly maintained a link to these steps in his .sig file.
*This does not apply to the DI-704 DI-704P DI-713 DI-713P DI-714P+ DI-804HV or DI-808HV. Please see »support.dlink.com/supportfaq to look up your router. Then find the procedure either under Reset Procedure or Troubleshooting.
**For help with this step, see /faq/12856
Feedback received on this FAQ entry:
To determine if it is only your Internet connection that is suffering, see if you are able to ping your router and other machines on your LAN, and transfer files at normal speeds. If you can do these tasks, then try the suggestions contained in this FAQ entry:
Established TCP connections will not be broken by the rule, and so it will seem like the rule is not working.
However, UDP and ICMP are connectionless forms of communication. If the software uses UDP, the firewall rule will seem to take effect immediately.
There is a possible work-around that allows breaking existing TCP connections discussed here: »DI-604 alternative
To determine if this issue is happening to your router, you must check the log and look for error messages concerning DHCP Discover or DHCP Renew requests that "time out" (go unanswered).
If you see these error messages, follow the suggestions contained in this FAQ entry:
"Gamefuel should be enabled on that router as it provides an essential feature. However, in order for the router to properly classify traffic is must first know the WAN upload speed (as the only scheduling the router performs is upload scheduling), and second it must be able to accurately classify traffic.
When the router determines that you are transmitting too much traffic, and are thus saturating your uplink the router will schedule traffic. If there is too much traffic scheduled it will run out of buffer space, and you will lose your WAN connection, and in some cases the router will become unresponsive until the buffers clear.
In order to alleviate that problem set the WAN uplink to EXACTLY the number quoted to you by your ISP. Then create rules for Bittorrent that place them as one of the lowest priorities, and rules for your high priority traffic.
Although dynamic classification can help to fully enjoy the benefit from QoS upload scheduling you should attempt to manually create rules for your most and lease important traffic, and then rely on dynamic classification for all that falls in between."
joe_dude suggests creating a rule for bittorrent port(s) with a priority of 255 for TCP and UDP (for DHT).
This was discussed in /forum/remark,14541688 ...
I had this same problem. When I searched for how to reset, I found two instructions.
If the router locks up very shortly (or immediately) after applying power, the likely cause is a power source that is not supplying the correct output power. Suggestion: Near the power input, you can read the required rating and polarity of the power supply. Ensure you are using the correct power supply. If you suspect that your power supply is failing and is no longer producing the rated voltage, amperage, and polarity cleanly, you should replace it with another power supply of the same specifications.
The following steps discuss updating the firmware. If your router is a wireless version of the router, you should only update the firmware using a Ethernet cable connection.
Of course, you should first double-check that your firmware version is correct for your router's model and hardware version. The hardware version is listed on a sticker attached to the bottom of the router.
In the above example, note that the hardware (H/W) version is B2. Generally, any firmware designed for "Rev B" of the device can be applied, unless there is a specific direction on the D-Link site concerning a specific step-release (example: B2).
Note: Some firmware versions contain features designed and tested appropriate to the local geography's ISP specifications and laws. If you are having problems, and you have a firmware from another geography, apply the latest firmware from your own geography to see if it resolves your issue. D-Link may be reluctant to support your use of a firmware not designed and tested for your geography.
Step 2 (if needed):
Simply try again. Sometimes the file transfer fails.
Step 3 (if needed):
If you are using the correct firmware for your router, and you are still receiving an error indicating that the firmware is an incorrect version, you should follow these steps:
1. In your router's web configuration, navigate to Tools / System
2. Click on "Restore to Factory Default"
(Note: To continue beyond this point, you may need to adjust your computer to match the default settings. The router's IP address is 192.168.0.1, and the admin password is blank.)
3. Disconnect power from the router for a few moments, then reconnect it
4. Repeat your attempt to update the firmware
Step 4 (if needed):
If you continue to receive the error, follow the steps included in this FAQ answer:
Hint: After applying a new firmware, it is a recommendation of many Broadband Reports users that you reconfigure your router manually instead of using the "Load Settings From Local Hard Drive" feature found on Tools / Status.
http://www.dyndns.com/support/clients/ ). This is likely to become a permanent solution for any product that is no longer supported by its manufacturer.
You can read more about this at http://www.dyndns.com/about/company/notify/archives/useragent_block_client10.html.
This was discussed in this topic, /forum/remark,14702251, but please note that the issue affects many more products than the DI-604.
When the router detects that there are an extreme and rising number of network errors, or detects other signs that the network is malfunctioning, a router is designed to automatically reboot. This reboot is in hopes that normal operation can be reestablished, rather than a total network outage.
However, if this detection itself malfunctions and those conditions cannot be detected, the malfunctioning router will crash.
Typical signs of a crash are
•the router's configuration pages do not respond, and
•you cannot ping the router, anything connected to the router, or anything on the Internet
Because crashes and reboots are closely related, the possible causes and solutions are the same.
Please see this FAQ for more information and possible ways to avoid a crash:
»D-Link Forum FAQ »Why does my router or AP reboot or crash? What can I do to avoid it?
Feedback received on this FAQ entry:
The IP address and port number of the LAN-side application.
The communications protocol used for the conversation.
The IP address and port number of the WAN-side application.
The port number of the LAN-side application as viewed by the WAN-side application.
The preference given to outbound packets of this conversation by the GameFuel logic. Smaller numbers represent higher priority.
State for sessions that use the TCP protocol.
NO: None -- This entry is used as a placeholder for a future connection that may occur.
SS: SYN Sent -- One of the systems is attempting to start a connection.
EST: Established -- the connection is passing data.
FW: FIN Wait -- The client system has requested that the connection be stopped.
CW: Close Wait -- the server system has requested that the connection be stopped.
TW: Time Wait -- Waiting for a short time while a connection that was in FIN Wait is fully closed.
LA: Last ACK -- Waiting for a short time while a connection that was in Close Wait is fully closed.
CL: Closed -- The connection is no longer active but the session is being tracked in case there are any retransmitted packets still pending.
The direction of initiation of the conversation:
Initiated from LAN to WAN.
Initiated from WAN to LAN.
The number of seconds of idle time until the router considers the session terminated. The initial value of Time Out depends on the type and state of the connection.
Reset or closed TCP connections. The connection does not close instantly so that lingering packets can pass or the connection can be re-established.
Opening or closing TCP connections.
Established TCP connections.
Submitted by mb
snowkilts had this problem, reported it, and then resolved it, "In case anybody else runs into the same problem, the fix is to go into the router configuration (on this router the address is 192.168.0.1) as follows : ADVANCED tab, FIREWALL SETTINGS screen, and then under APPLICATION LEVEL GATEWAY CONFIGURATION, uncheck the box next to RTSP, scroll back to the top of the screen and save the settings."
This affects/affected DIR-625 and Real Player, DIR-615 and DIR-625 and Windows Media Player. With RTSP enabled, Real Player says "connecting" until it times out with a network error. In effect, "having the box checked blocks this protocol." Unchecking the RTSP ALG box allowed the communication to pass through the device properly.