Acquiring network address:weird

[OldNick]

Router = Draytek 2910VG
OpSys = XP sp2 Home
network car = d-link GDWA-510 wireless
Normal F/W Comodo Pro

At bootup, everything is fine. This happens when I try to connect to the network when the PC is running.

When I attempt to connect to the network (router) I can connect OK, but then the connector icon just says "Acquiring network address".

Now here's the weird bit (I hope not _too_ weird). It will sit there and do this until I alter the XP firewall setting from Off to On, then, repeatably and instantly, it gets an address. Note: the XP FW was OFF and I turned it ON.

Then if I try again, it sits there until I again try changing the XP FW to OFF, from ON, then again I have instant access.

So I completely disabled XP FW, by using Services.msc, and all that happened is that I now cannot acquire a network address at all! Because there is no Windows Network to alter....

I have tried to also close down my own FW, and the router's. This does not work.

My networks are set up to be assigned an auto address by the router. The system is encrypted. But it has been for ever.

But this has started in the last couple of days. I am not aware of any changes I have made to the system that could have caused it.

The Comodo FW did show traffic being stopped, and the active process was svchost.exe. This could be bad, except that killing the FW makes no difference.

Anyone any ides?

Thanks

Nick

[devamfl]

Originally Posted by OldNick

Router = Draytek 2910VG
OpSys = XP sp2 Home
network car = d-link GDWA-510 wireless
Normal F/W Comodo Pro

At bootup, everything is fine. This happens when I try to connect to the network when the PC is running.

When I attempt to connect to the network (router) I can connect OK, but then the connector icon just says "Acquiring network address".

Now here's the weird bit (I hope not _too_ weird). It will sit there and do this until I alter the XP firewall setting from Off to On, then, repeatably and instantly, it gets an address. Note: the XP FW was OFF and I turned it ON.

Then if I try again, it sits there until I again try changing the XP FW to OFF, from ON, then again I have instant access.

So I completely disabled XP FW, by using Services.msc, and all that happened is that I now cannot acquire a network address at all! Because there is no Windows Network to alter....

I have tried to also close down my own FW, and the router's. This does not work.

My networks are set up to be assigned an auto address by the router. The system is encrypted. But it has been for ever.

But this has started in the last couple of days. I am not aware of any changes I have made to the system that could have caused it.

The Comodo FW did show traffic being stopped, and the active process was svchost.exe. This could be bad, except that killing the FW makes no difference.

Anyone any ides?

Thanks

Nick

Have you tried to uncheck the Qos protocol on your adapter settings?\
Also try to disable the network adapter in device manager and restart
the only other thing might be that your nic card is throwing out bad packets
and confusing the router.
Finaly try removing tcpip and re-adding

[OldNick]

This is a blast from the past! <G>

Thanks for the reply. I will try what you suggest, although QOS is needed because I use VOIP over wireless B/B, which has enough quirks of its own and needs to be given very high priority.

My only clue in all of this is that when I reboot, the network connects OK. Only if I try to reconnect with the PC running does it have any trouble.

Nick

[devamfl]

mmm If things work ok on a re-boot, I suggest you power down you computer
open the case and clean out any dust also re-seat you nic card, the contacts probably have become dusty and cause packet loss. Sounds hard to believe but many of the new generation computers (especialy dual proc and quad core) behave erraticaly because of dust build up that is causing temp fluctations.

[OldNick]

OK. Thanks. I have cleaned the PC recently (thoroughly; HS and fan off and cleaned etc., but I will check all the cards and slots for dirt or rust.

It is amazing how hot a CPU can get very fast. One time I did not set the HS properly,and the PC would shut down after about 10 seconds or less. I took the fan off and the CPU was still unpleasantly warm.

Nick

[devamfl]

DO you have a fan on your processor as well as external in the case?

Processor fan is effiecient however, depends on the foot print of you computer.

I vacuum the external vent which clogs up with dust every week to keep
the circulation healthy.

Do make sure you unplucg the computer and ground any static off your body so you don't
zap anything. I find that if you power down and then touch the chassis before unplugging buys you
enough time to do a general clean up or invest in a wrist strap.

[OldNick]

Howdy. I am back.

My PC does have some sort of issue. Every now and then it just reboots. This could well be a heat thing.

However, here is another clue (distraction?). When I boot up, the network (secure wireless) connect automatically. but when I disconnect and connect manually, I have to OK a pre-entered password and username. Than is when I have change the Win FW's state from off to on to get an address. I then immediately set it off again.

Thanks for the input.

Nick

[devamfl]

Originally Posted by OldNick

Howdy. I am back.

My PC does have some sort of issue. Every now and then it just reboots. This could well be a heat thing.

However, here is another clue (distraction?). When I boot up, the network (secure wireless) connect automatically. but when I disconnect and connect manually, I have to OK a pre-entered password and username. Than is when I have change the Win FW's state from off to on to get an address. I then immediately set it off again.

Thanks for the input.

Nick

Have you tried to turn off firewall and see it still happens. check the firewall settings. Install sp3

[webhosting]

Originally Posted by devamfl

Have you tried to turn off firewall and see it still happens. check the firewall settings. Install sp3

cool Sp3 seems to be working. Thanks