how-to block ads
|
| | | | FAQ Revisions | Editors: kmac1  , xDSLMan , Aria73
Last modified on 2008-09-21 09:05:27
| |
|
|
10. Troubleshooting·How can I tell if I have a marginal DSL line?
·Where do I find the management logs for a 2Wire Homeportal?
·Intermittant connection after refreshing game browser/many client connections
·Problems installing the PC Port / or any USB powered network device
·Problems loading the PC-Port on a Win98 1st Edition Machine.
·Homeportal sluggish or nonresponsive after opening up ports on firewall
·2wire reboots/resets itself frequently
| | | 2Wire modems have a number of indicators for DSL line quality. There are informational displays on the main user interface (http: //homeportal) under the Broadband Link tab: Details, but this same information and much more is available through the Management and Diagnostic Console (http: //homeportal/mdc/).
Using this 2Wire Homeportal 1000HG as an example, we can see the effects of being a long distance away from the Central Office and having a phone line that picks up some noise.
This is the Broadband Link - Statistics page of the MDC ( »homeportal/mdc/ )
The first thing to notice here in the Downstream section is the Current Rate is 1440 and the Max Rate is 1440. The ordered package is 768-1.5Meg and right now the line is synced at 1440. 100% of the available downstream space on the line is in use. The Current noise Margin at 8dB is very low and the Current Attenuation at 59dB is very high. All indicate this line is just about tapped out, in truth on good days this line will give a full 1.5Meg sync, but there is no way we could ever order the 3.0Meg package for it, it would never hold.
A better line would have a higher Noise Margin. 6dB is about as low as you can go. Numbers above 10dB are better, and above 16dB superb. Attenuation numbers above 60dB are poor, and above 64dB are just about unusable. Better lines would be in the 20-50dB range.
This page is the Troubleshooting - DSL Diagnostics display of the MDC - And is available on software versions 3.5.11 and higer-
Here we see another reason this line is not holding the maximum 1.5Meg sync. This line is seeing impulse nose and the 2Wire is calling it Suspicious. Here you might start looking around your installation for things that could be generating noise on your home line. Electrical dimmers, lights, wireless phones, motors, the computer itself or a printer, etc. near your phone line. If the noise source is in your home, you can correct it - try running a new phone line and using an NID splitter. Move the modem at least 3 feet away from anything that can produce electrical noise.
In this case the noise is outside the home as an new line and splitter were already installed, so there is little more that can be done inside.
Another line of this display is Uncancelled Echo - This would be reading suspicious if you had forgotten to put a filter on every phone, fax, tivo, cable box, alarm, etc. in the home. This reading would be high because an unfiltered device could cause more echo then the modem can compensate for and thus lead to lower sync rates. This does not always happen, but if you get a Suspicious reading for Uncancelled Echo, filters are the first thing to check!
The Training History shows the status of various readings each time the modem has to re-sync itself to the line. It gives the date and time and indications of the Sync rates and other readings. Using this information you can get an overall picture as to how well your line is performing over time and if problems are due to retrains or something else.
Looking at this history, you can see that for a few days we had a sync rate at the maximum for the package: 1536, and had some room to spare in the 1920-1984 range. The noise margins were low, in the 5dB to 7dB range and the Attenuation high. CRC are Cyclic Redundancy Checks on the data, and it is normal to have some errors, especially on a marginal line.
You can see a period of time between 3/21 and 3/28 where we held 1536 for 7 days, then we retrained every couple of days. It is not uncommon to go weeks or a month or 2 without a retain on good lines.
Here is the right side of the Training History, and the Impulse Noise Tones. The Exit Code gives you an indication of what caused the retrain. In most cases here it was Loss Of Signal Limit, but there are others.
If you have a higher speed package, and you are not getting the full sync, these displays may help give you an idea why and what to look for. If its Suspicious Echo, look at your Filters. If its Noise Tones, look for items that generate electrical noise near the phone line or move the phone line. If the noise is from outside your home there may be little you can do about it. If you see a steady decrease in sync rates over time, along with an increase in Attenuation and decrease in Noise Margin you may have a phone line that has bad splices or jumpers. If you also hear static on the line this would be a good indication and you should run an NID test by plugging you modem directly in at the NID test jack. If your numbers improve at the NID then your problem is in your house wiring and you need to track it down. If they do not improve the problem is in the outside phone line and you need to have it checked. Not all lines can support all speeds, so you have to see what the DSL provider can do. Installing a NID splitter and pulling a home run cat 5 cable is not a bad idea, but if your numbers are low to start with this may only be of marginal help - but can go a ways to help eliminate poor inside wiring and missed filters.
-Riss_Centaur
 feedback form
 feedback form
by Riss_Centaur
last modified: 2005-04-05 00:44:15 | | | The Management and Diagnostic Console (MDC) is for advanced troubleshooting in the event of trouble. Access it by going to »homeportal/management or »172.16.0.1/management. Later model units may be using the 192.168.1.254 address so the MDC may be found here: »192.168.1.254/management
(/MDC will also work in place of /management)
The 2Wires maintain 2 logs. The first - Event Log (under Troubleshooting) is software oriented and mostly lists firewall hits and minor events with settings.
The second - Detailed Log (under Advanced) is more hardware oriented (equivalent to a unix Syslog) and is of more help to track down problems with the 2Wire itself.
Sometimes you may be asked to copy and paste the contents of these logs to a message on the board so others can inspect them for trouble if you are asking for help with an issue.
Updated 1/3/06-R_C
feedback form
feedback form
by KeysCapt edited by Riss_Centaur
last modified: 2006-01-04 20:46:52 | | | The homeportal has an inherant software limitation of 512 Entries in the NAT (Natural Address Translation) lookup table. It uses this table to route packets from the WAN Internet interface to the computers on your internal LAN interface properly. The homeportal defaults to a timeout of 1440! minutes for a TCP connection such as web browsing/ftp/usenet and a timeout of 10 minutes for a UDP connection such as Gaming, voice comms, or other real time tasks.
When the maximum amount of entries in the NAT tables are reached (by connecting to 512 different servers in less than the timeout period, such as updating a game browser or heavy p2p use) the Homeportal simply refuses to service any further connection attempts until some entries free up on the NAT table by current connections timing out. This may take 10 minutes or more depending on the type of connections in use.
Under the NAT section on »home/tech/configuration.html there is a setting for TCP Timeout and UDP Timeout, setting these to the lowest possible values (5 minutes, and 1 minute respectively) will help mitigate these issues. However if you try and update a game browser that has more than 512 servers listed, it will refuse to show you any servers beyond that 512th server on the list because the Homeportal is not making connections.
The workaround for this issue is to limit the game browser to using only 7 packets per second (7 pps x 60 seconds = 420 packets, which leaves almost entries in the NAT table free to prevent overloading)
One of the game browsers I know will allow you to limit the number of packets per second is the All Seeing Eye: »www.udpsoft.com/eye2/index.html It supports a whole lot of games, and allows you to limit the packets per second to 6 or 7, this, combined with setting the UDP timeout on the homeportal »home/tech/configuration.html to the lowest possible allows an effective work-around. This will allow you to see every server on the list beyond 512 servers, however it's going to be a lot slower than letting the list update the normal way.
-----------------------------------------------------
Note: In firmware version 3.7.1 and above, the NAT table was increased to 1024 entries to help reduce the table overload problem.
-R_C 4/21/05
feedback form
feedback form
by Da_G edited by Gargoyle
last modified: 2007-02-20 07:38:16 | | | 1) Verify that your usb root hubs are not set to "Turn this device off to save power". If so remove that check from the power management tab in the device manager properties of the root hubs.
2) If you are having problems installing the PC Port there is a key step to resolving this. Microsoft's "Root Hub" is, well, buggy.
The easiest way to get the PC Port to install is to do the following steps:
• Remove any Unknown Devices
• Remove any instances of the PC Port
• Remove the USB Root hub
(BEWARE! this removes all usb devices, so if you have USB keyboard and mouse they will stop working)
• Reboot After rebooting, your hardware should be correctly identified (including PC Port) and the correct drivers from the CD should be installed.
From a post by gzminiz
feedback form
feedback form
by KeysCapt edited by Riss_Centaur
last modified: 2005-09-25 08:45:42 | | | A. You need to load the patch program supplied on the 2Wire CD. It can be found in the \Utils\PCPort_Update_98Gold\PCP98GUp folder of the CD.
feedback form
feedback form
by systech edited by KeysCapt
last modified: 2003-07-16 11:25:18 | | | Some firmware versions in the homeportal seems to have a poor software implementation of port forwarding, and this shows through when you try to open up a large range of ports in the firewall (500-10000+ ports?). The homeportal starts refusing to honor requests to access it's internal configuration pages, and ping times skyrocket. Other issues may also occur as a result. The following steps will return your homeportal to factory state in this condition so that you will be able to use it again without returning it to 2wire for a firmware flashing.
DMZPlus Mode should be used for any computer that needs to have many ports forwarded to it.
Use the following or the original method below.
Easier method:
1) Unplug the phone line from the Homeportal so it can not go online.
2) Power cycle the home portal.
3) After the Local Network light goes green, see if you can access the configuration pages at http://homeportal (or by the IP address).
4) Reset the firewall to not have many ports open. (or do a factory reset and reconfigure from the original setup)
5) Reconnect the phone line to restore connectivity.
========================================================
Original method:
1. Open up your web browser and type in the known address/management (http://172.16.0.1/management/ is default. Later model units may be using the 192.168.1.254 address so the MDC may be found here: http://192.168.1.254/management/) DO NOT PRESS THE ENTER KEY YET.
2. Disconnect the power from the Homeportal for about 20 seconds then reconnect.
3. Once you see the local network light turn green (bottom light) PRESS THE ENTER KEY ON THE KEYBOARD. You have a small amount of time to work with.
4. Type in your password (if you had set one) and you should be at the Management and Diagnostic Console window. Scroll down to the Troubleshooting section on the menu at left and select Resets. You need to write down you activation key code before you press the reset because you will need it to reconfigure your homeportal. (or look it up on the 2wire site)
5. Right at this point you may be out of time. Start the process all over and this time, reset the homeportal back to it's factory state. (bottom reset button on that page)
Thanks to dwhall29 for this fix.
---------
Updated 3/2006 -R_C
feedback form
feedback form
by Da_G edited by Riss_Centaur
last modified: 2006-03-10 12:00:27 | | | I noticed a fair amount of posts with a similar problem, and found a reply from jakethecat that is pretty much verbatim with what the ATT tech support said. I thought it would be a good entry to the FAQ. (btw, I have a 2701HG-B, and resetting to factory defaults is what fixed my problem)
said by jakethecat :Three general things will cause a 2Wire to reboot with out permission. 1. The power going into the 2Wire is unstable - corrected by moving it to a different circuit or connecting it through UPS. 2. The 2Wire (or it's power supply) is no longer functioning properly on a physical level - hit up support@2wire.com and see if they will send you a new power supply (or your ISP for a full replacement if you are within warranty). 3. The software running the 2Wire is not in a stable state - reset your 2Wire to factory state by holding the little red button in the back for 30 seconds. If the issue persists, disconnect all computers from the 2Wire. If it still reboots the 2Wire may need replacing. and 4. Tech support additionally told me to run SpyBot to make sure there wasn't anything on the computer that shouldn't be, trying to open too many sessions.
feedback form
feedback form
by monty4 edited by Aria73
last modified: 2007-05-28 21:35:02 |
|
