I have no problem when using Azureus 3.0.3.4 on the other two machines on
the network connected wirelessly to the D-Link DI-624 router. However in the
case of the machine connected directly to the router, after sometime using
Azureus, all network activity stops. I can still ping the machine's DHCP
assigned address as well as the localhost 127.0.0.1. The default gateway as
well as any other address on the network are unresponsive. If the network
cable is unplugged, XP reports "cable unplugged". Repair of the network
connection results in an obscure Automatic Private Address rather than the
router DHCP reserved 192.168.0.128. When examining Local Area Connection
Properties, the window stops responding and Explorer restarts when Task
Manager is used to end the unresponsive program.
Up to now, the only fix for this problem is to reboot the machine, although
on shutdown, the system hangs indefinitely with "Closing Network
Connections", so a box reset is necessary. The network card is a SiS 190
100/10 Ethernet Device which has been uninstalled and reinstalled, and has
had it driver updated to version 2.0.1029.1090 dated 15/10/2007. In Device
Manager were some old network devices listed but not present, which were
eventually removed after uninstalling the QoS Packet Scheduler service. The
TCP/IP stack has been reset and also the Winsock has been repaired using XP
TCP/IP Repair Utility.
It is reported in the Azureus Wiki http://www.azureuswiki.com/index.php/Bad_routers that my DI-624 router is
considered "bad" and "has known problems with too many global connections.
Limiting it to 200 or less should fix the problem." This has been done in
Azureus options but the problem remains on the machine that is not connected
wirelessly. Except when using Azureus, the network works flawlessly both in
the Local Area Network and to the Internet.
Are there any further tests that could be done that would prove if this a XP
problem or hardware?
As my post has gone unanswered, I wonder if I posted it in the correct
newsgroup??
Thanks, Martyn
"MartynB" <anonymous@discussions.microsoft.com> wrote in message
news:eb4q4GcMIHA.6060@TK2MSFTNGP05.phx.gbl...
> This machine is XP Pro SP2 fully updated.
>
> I have no problem when using Azureus 3.0.3.4 on the other two machines on
> the network connected wirelessly to the D-Link DI-624 router. However in
> the case of the machine connected directly to the router, after sometime
> using Azureus, all network activity stops. I can still ping the machine's
> DHCP assigned address as well as the localhost 127.0.0.1. The default
> gateway as well as any other address on the network are unresponsive. If
> the network cable is unplugged, XP reports "cable unplugged". Repair of
> the network connection results in an obscure Automatic Private Address
> rather than the router DHCP reserved 192.168.0.128. When examining Local
> Area Connection Properties, the window stops responding and Explorer
> restarts when Task Manager is used to end the unresponsive program.
>
> Up to now, the only fix for this problem is to reboot the machine,
> although on shutdown, the system hangs indefinitely with "Closing Network
> Connections", so a box reset is necessary. The network card is a SiS 190
> 100/10 Ethernet Device which has been uninstalled and reinstalled, and has
> had it driver updated to version 2.0.1029.1090 dated 15/10/2007. In Device
> Manager were some old network devices listed but not present, which were
> eventually removed after uninstalling the QoS Packet Scheduler service.
> The TCP/IP stack has been reset and also the Winsock has been repaired
> using XP TCP/IP Repair Utility.
>
> It is reported in the Azureus Wiki
> http://www.azureuswiki.com/index.php/Bad_routers that my DI-624 router is
> considered "bad" and "has known problems with too many global connections.
> Limiting it to 200 or less should fix the problem." This has been done in
> Azureus options but the problem remains on the machine that is not
> connected wirelessly. Except when using Azureus, the network works
> flawlessly both in the Local Area Network and to the Internet.
>
> Are there any further tests that could be done that would prove if this a
> XP problem or hardware?
>
On Nov 30, 10:11 am, "MartynB" <anonym...@discussions.microsoft.com>
wrote:
> As my post has gone unanswered, I wonder if I posted it in the correct
> newsgroup??
>
> Thanks, Martyn
>
> "MartynB" <anonym...@discussions.microsoft.com> wrote in message
>
> news:eb4q4GcMIHA.6060@TK2MSFTNGP05.phx.gbl...
>
>
>
> > This machine is XP Pro SP2 fully updated.
>
> > I have no problem when using Azureus 3.0.3.4 on the other two machines on
> > the network connected wirelessly to the D-Link DI-624 router. However in
> > the case of the machine connected directly to the router, after sometime
> > using Azureus, all network activity stops. I can still ping the machine's
> > DHCP assigned address as well as the localhost 127.0.0.1. The default
> > gateway as well as any other address on the network are unresponsive. If
> > the network cable is unplugged, XP reports "cable unplugged". Repair of
> > the network connection results in an obscure Automatic Private Address
> > rather than the router DHCP reserved 192.168.0.128. When examining Local
> > Area Connection Properties, the window stops responding and Explorer
> > restarts when Task Manager is used to end the unresponsive program.
>
> > Up to now, the only fix for this problem is to reboot the machine,
> > although on shutdown, the system hangs indefinitely with "Closing Network
> > Connections", so a box reset is necessary. The network card is a SiS 190
> > 100/10 Ethernet Device which has been uninstalled and reinstalled, and has
> > had it driver updated to version 2.0.1029.1090 dated 15/10/2007. In Device
> > Manager were some old network devices listed but not present, which were
> > eventually removed after uninstalling the QoS Packet Scheduler service.
> > The TCP/IP stack has been reset and also the Winsock has been repaired
> > using XP TCP/IP Repair Utility.
>
> > It is reported in the Azureus Wiki
> >http://www.azureuswiki.com/index.php/Bad_routersthat my DI-624 router is
> > considered "bad" and "has known problems with too many global connections.
> > Limiting it to 200 or less should fix the problem." This has been done in
> > Azureus options but the problem remains on the machine that is not
> > connected wirelessly. Except when using Azureus, the network works
> > flawlessly both in the Local Area Network and to the Internet.
>
> > Are there any further tests that could be done that would prove if this a
> > XP problem or hardware?- Hide quoted text -
>
> - Show quoted text -
Yes, this is a "good" group for network question but Azureus is not a
Microsoft product. It will take time for possible answers to come.
You might want to:
1) Limiting to lesser connection as most P2P system are still frowned
on and several ISP are starting to block this type of traffic.
2) Replace the "bad" router with a different make / model
3) Check for possible "firmware" updates to this router. NOTE:
Firmware updates "erase" all / most configurations in router and you
need to re-porgram them.
Network connection dies during Azureus 
Linear Mode
