Broadband Disconnects
A client reported that a USB broadband modem performed well when browsing the internet but as soon as he attempted to download anything more than about 2MB it either disconnected immediately or sent the error message "Tapisrv has caused an error in rpcrt4.dll and will now close". A reboot was then required.
This error has many possible causes. Quite a lot of people have this problem, especially with Windows Me, but Microsoft has not documented a fix for it. Some cynics have suggested that you need to upgrade to another operating system.
There is another possible solution. Sometimes this problem can arise through incompatible settings for the TCP/IP configuration parameter called MaxMTU. By default, Windows uses a value of 1500 but PPoE, which is used by most ADSL modems, adds a little bit of overhead to each packet. Reducing the MaxMTU value to 1,400, for example, may cure the problem for you. Try using Tweak DUN from www.pattersondesigns.com/tweakdun to achieve this.
If this doesn't help, things get more complicated. The problem could be due to corruption in the Registry settings or the TAPI files.
It could be a buggy driver for your ADSL modem, bugs in the hardware software implementation of USB or bugs in Windows Me.
It could also be a hardware issue, either with a faulty USB modem or a computer that can't provide enough power to the USB port. Many USB modems take their power from the USB port and use close to the maximum power that the USB specification permits. Sometimes plugging the modem into another USB port or using a powered USB hub can cure this.
Replacing the USB ADSL modem with a standalone ADSL modem router, which connects to your PC by Ethernet, may be the best way to stop the problem, and will also allow you to connect a second PC. Get a wireless router and you may be able to share the cost of the connection with your neighbours!
Unfortunately, if you want to keep the USB modem, upgrading from Windows Me to XP may be your best solution. If you don't want to upgrade to Windows XP, which has greatly improved support for DSL modems, first look for newer drivers for your ADSL modem.
This error has many possible causes. Quite a lot of people have this problem, especially with Windows Me, but Microsoft has not documented a fix for it. Some cynics have suggested that you need to upgrade to another operating system.
There is another possible solution. Sometimes this problem can arise through incompatible settings for the TCP/IP configuration parameter called MaxMTU. By default, Windows uses a value of 1500 but PPoE, which is used by most ADSL modems, adds a little bit of overhead to each packet. Reducing the MaxMTU value to 1,400, for example, may cure the problem for you. Try using Tweak DUN from www.pattersondesigns.com/tweakdun to achieve this.
If this doesn't help, things get more complicated. The problem could be due to corruption in the Registry settings or the TAPI files.
It could be a buggy driver for your ADSL modem, bugs in the hardware software implementation of USB or bugs in Windows Me.
It could also be a hardware issue, either with a faulty USB modem or a computer that can't provide enough power to the USB port. Many USB modems take their power from the USB port and use close to the maximum power that the USB specification permits. Sometimes plugging the modem into another USB port or using a powered USB hub can cure this.
Replacing the USB ADSL modem with a standalone ADSL modem router, which connects to your PC by Ethernet, may be the best way to stop the problem, and will also allow you to connect a second PC. Get a wireless router and you may be able to share the cost of the connection with your neighbours!
Unfortunately, if you want to keep the USB modem, upgrading from Windows Me to XP may be your best solution. If you don't want to upgrade to Windows XP, which has greatly improved support for DSL modems, first look for newer drivers for your ADSL modem.
If that doesn't help, you might want to try installing a program called RASPPPOE from www.raspppoe.com. This provides a replacement for the standard Windows remote access software, which is where the error is.
Posts
0 comments:
Post a Comment