XP SP2: Wireless connection takes a while to automatically start up..

Hello,

I've TrendNet PCMCIA WiFi adapters in 2 systems to connect in 802.11g to an
AP/Router SMC2804WBR.
For weeks now, I'm facing a recurrent problem when starting the WiFi
connection on each system . The radio connection is well detected but it
can takes minutes to hours to establish the final IP connection either in
fixed IP or in DHCP IP. ( it's looping in "Waiting for Network").

When connection is successful, after, it works fine with good signal and
speed.

It's not a question of signal strengh or quality because NetStumbler is
detecting a very good radio connection.

I went through the forums and find many persons pointing the same problem
and situation with SP2, I installed the correction "WinsockXPFix.exe"
proposed by MS, but it doesn't solve my problem.

My guess is that's related to the new way of processing WiFi which arrived
with SP2 ... I discussed with TRENDNET TechSupport and they don't see any
solution ...

Does somebody has new ideas and can help me solving this problem?

Thanks in advance
--
Cordialement / Regards
Castor , e-quinqua

enlever le ~ pour utiliser l'adresse courriel
withdraw the ~ to use email address

"Castor" wrote in message
...
Hello,

I've TrendNet PCMCIA WiFi adapters in 2 systems to connect in 802.11g to
an AP/Router SMC2804WBR.
For weeks now, I'm facing a recurrent problem when starting the WiFi
connection on each system . The radio connection is well detected but it
can takes minutes to hours to establish the final IP connection either in
fixed IP or in DHCP IP. ( it's looping in "Waiting for Network").

When connection is successful, after, it works fine with good signal and
speed.

It's not a question of signal strengh or quality because NetStumbler is
detecting a very good radio connection.

I went through the forums and find many persons pointing the same problem
and situation with SP2, I installed the correction "WinsockXPFix.exe"
proposed by MS, but it doesn't solve my problem.

My guess is that's related to the new way of processing WiFi which arrived
with SP2 ... I discussed with TRENDNET TechSupport and they don't see any
solution ...

Does somebody has new ideas and can help me solving this problem?


You say you use Netstumbler but to the best of my knowledge it doesn't pick
up cloaked networks and that is exactly what you may be experiencing - a
cloaked network on the same channel, nearby.

Try setting the channel to something other than what you currently use and
see if that helps.

You could also be having a problem with firewalls. Take them all offline and
see what happens.

"Interrogative" a écrit dans le message de news:
...

"Castor" wrote in message
...
Hello,

I've TrendNet PCMCIA WiFi adapters in 2 systems to connect in 802.11g to
an AP/Router SMC2804WBR.
For weeks now, I'm facing a recurrent problem when starting the WiFi
connection on each system . The radio connection is well detected but it
can takes minutes to hours to establish the final IP connection either in
fixed IP or in DHCP IP. ( it's looping in "Waiting for Network").

When connection is successful, after, it works fine with good signal and
speed.

It's not a question of signal strengh or quality because NetStumbler is
detecting a very good radio connection.

I went through the forums and find many persons pointing the same problem
and situation with SP2, I installed the correction "WinsockXPFix.exe"
proposed by MS, but it doesn't solve my problem.

My guess is that's related to the new way of processing WiFi which
arrived with SP2 ... I discussed with TRENDNET TechSupport and they don't
see any solution ...

Does somebody has new ideas and can help me solving this problem?


You say you use Netstumbler but to the best of my knowledge it doesn't
pick up cloaked networks and that is exactly what you may be
experiencing - a cloaked network on the same channel, nearby.
*** As far as I've experienced there are no other network broadcasting
around ... It works fine with my old Wifi 802.11b ELSA adapters ...


Try setting the channel to something other than what you currently use and
see if that helps.
*** Changing channels number doesn't change the result ...

You could also be having a problem with firewalls. Take them all offline
and see what happens.
*** With or without firewalls on it's the same...



***As I wrote in my initial message , after a waiting time looping on
"Waiting for network" it connects well and it can work for hours ...

****It's really a problem of establishing the connection after activating it
....

So, ... Thanks for your interest in my problem ..

"Castor" wrote in message
...

"Interrogative" a écrit dans le message de
news: ...

"Castor" wrote in message
...
Hello,

I've TrendNet PCMCIA WiFi adapters in 2 systems to connect in 802.11g to
an AP/Router SMC2804WBR.
For weeks now, I'm facing a recurrent problem when starting the WiFi
connection on each system . The radio connection is well detected but
it can takes minutes to hours to establish the final IP connection
either in fixed IP or in DHCP IP. ( it's looping in "Waiting for
Network").

When connection is successful, after, it works fine with good signal and
speed.

It's not a question of signal strengh or quality because NetStumbler is
detecting a very good radio connection.

I went through the forums and find many persons pointing the same
problem and situation with SP2, I installed the correction
"WinsockXPFix.exe" proposed by MS, but it doesn't solve my problem.

My guess is that's related to the new way of processing WiFi which
arrived with SP2 ... I discussed with TRENDNET TechSupport and they
don't see any solution ...

Does somebody has new ideas and can help me solving this problem?


You say you use Netstumbler but to the best of my knowledge it doesn't
pick up cloaked networks and that is exactly what you may be
experiencing - a cloaked network on the same channel, nearby.
*** As far as I've experienced there are no other network broadcasting
around ... It works fine with my old Wifi 802.11b ELSA adapters ...


Try setting the channel to something other than what you currently use
and see if that helps.
*** Changing channels number doesn't change the result ...

You could also be having a problem with firewalls. Take them all offline
and see what happens.
*** With or without firewalls on it's the same...



***As I wrote in my initial message , after a waiting time looping on
"Waiting for network" it connects well and it can work for hours ...

****It's really a problem of establishing the connection after activating
it ...

So, ... Thanks for your interest in my problem ..


If that is the case, I would say you have signal attenuation of some sort,
then. My next suggestion is a signal booster/repeater somewhere between the
two. I get very occasionally, about 30 seconds of interval for the laptop's
external USB wi-fi Nic to attach to exactly the same make and model one on
this desktop machine. The laptop is at the other end of the house with 3
walls in between which encompass the bathroom, laundry (which also has the
freezer in it) and kitchen with all the usual kitchen appliances and volumes
of metal there. Normally I get top signal strength after that but
penetrating all those things causes an occasional lapse.

The way to test that thought is to put your two wi-fi machines in the same
room and see if you can repeat the performance they normally do. If you get
instant access, your problem will be helped or solved by a repeater.

"Interrogative" a écrit dans le message de news:
...

"Castor" wrote in message
...

"Interrogative" a écrit dans le message de
news: ...

"Castor" wrote in message
...
Hello,

I've TrendNet PCMCIA WiFi adapters in 2 systems to connect in 802.11g
to an AP/Router SMC2804WBR.
For weeks now, I'm facing a recurrent problem when starting the WiFi
connection on each system . The radio connection is well detected but
it can takes minutes to hours to establish the final IP connection
either in fixed IP or in DHCP IP. ( it's looping in "Waiting for
Network").

When connection is successful, after, it works fine with good signal
and speed.

It's not a question of signal strengh or quality because NetStumbler is
detecting a very good radio connection.

I went through the forums and find many persons pointing the same
problem and situation with SP2, I installed the correction
"WinsockXPFix.exe" proposed by MS, but it doesn't solve my problem.

My guess is that's related to the new way of processing WiFi which
arrived with SP2 ... I discussed with TRENDNET TechSupport and they
don't see any solution ...

Does somebody has new ideas and can help me solving this problem?


You say you use Netstumbler but to the best of my knowledge it doesn't
pick up cloaked networks and that is exactly what you may be
experiencing - a cloaked network on the same channel, nearby.
*** As far as I've experienced there are no other network broadcasting
around ... It works fine with my old Wifi 802.11b ELSA adapters ...


Try setting the channel to something other than what you currently use
and see if that helps.
*** Changing channels number doesn't change the result ...

You could also be having a problem with firewalls. Take them all offline
and see what happens.
*** With or without firewalls on it's the same...



***As I wrote in my initial message , after a waiting time looping on
"Waiting for network" it connects well and it can work for hours ...

****It's really a problem of establishing the connection after activating
it ...

So, ... Thanks for your interest in my problem ..


If that is the case, I would say you have signal attenuation of some sort,
then. My next suggestion is a signal booster/repeater somewhere between
the two. I get very occasionally, about 30 seconds of interval for the
laptop's external USB wi-fi Nic to attach to exactly the same make and
model one on this desktop machine. The laptop is at the other end of the
house with 3 walls in between which encompass the bathroom, laundry (which
also has the freezer in it) and kitchen with all the usual kitchen
appliances and volumes of metal there. Normally I get top signal strength
after that but penetrating all those things causes an occasional lapse.

The way to test that thought is to put your two wi-fi machines in the same
room and see if you can repeat the performance they normally do. If you
get instant access, your problem will be helped or solved by a repeater.


I did run tests with all the machines in the same room at a couple of meters
far from the AP/Router and it gave the result: very long waiting time to
connect ...
So, ...

"Castor" wrote in message
...

"Interrogative" a écrit dans le message de
news: ...

"Castor" wrote in message
...

"Interrogative" a écrit dans le message de
news: ...

"Castor" wrote in message
...
Hello,

I've TrendNet PCMCIA WiFi adapters in 2 systems to connect in 802.11g
to an AP/Router SMC2804WBR.
For weeks now, I'm facing a recurrent problem when starting the WiFi
connection on each system . The radio connection is well detected but
it can takes minutes to hours to establish the final IP connection
either in fixed IP or in DHCP IP. ( it's looping in "Waiting for
Network").

When connection is successful, after, it works fine with good signal
and speed.

It's not a question of signal strengh or quality because NetStumbler
is detecting a very good radio connection.

I went through the forums and find many persons pointing the same
problem and situation with SP2, I installed the correction
"WinsockXPFix.exe" proposed by MS, but it doesn't solve my problem.

My guess is that's related to the new way of processing WiFi which
arrived with SP2 ... I discussed with TRENDNET TechSupport and they
don't see any solution ...

Does somebody has new ideas and can help me solving this problem?


You say you use Netstumbler but to the best of my knowledge it doesn't
pick up cloaked networks and that is exactly what you may be
experiencing - a cloaked network on the same channel, nearby.
*** As far as I've experienced there are no other network broadcasting
around ... It works fine with my old Wifi 802.11b ELSA adapters ...


Try setting the channel to something other than what you currently use
and see if that helps.
*** Changing channels number doesn't change the result ...

You could also be having a problem with firewalls. Take them all
offline and see what happens.
*** With or without firewalls on it's the same...



***As I wrote in my initial message , after a waiting time looping on
"Waiting for network" it connects well and it can work for hours ...

****It's really a problem of establishing the connection after
activating it ...

So, ... Thanks for your interest in my problem ..


If that is the case, I would say you have signal attenuation of some
sort, then. My next suggestion is a signal booster/repeater somewhere
between the two. I get very occasionally, about 30 seconds of interval
for the laptop's external USB wi-fi Nic to attach to exactly the same
make and model one on this desktop machine. The laptop is at the other
end of the house with 3 walls in between which encompass the bathroom,
laundry (which also has the freezer in it) and kitchen with all the usual
kitchen appliances and volumes of metal there. Normally I get top signal
strength after that but penetrating all those things causes an occasional
lapse.

The way to test that thought is to put your two wi-fi machines in the
same room and see if you can repeat the performance they normally do. If
you get instant access, your problem will be helped or solved by a
repeater.


I did run tests with all the machines in the same room at a couple of
meters far from the AP/Router and it gave the result: very long waiting
time to connect ...
So, ...



Get HiJackThis and run a scan and save them and post them here. You said you
are manually assigning IPs and getting the same results. From all your
tests, all I can think is SOMETHING is starting at that time that is causing
this. I assume there is nothing other than TCP/IP in use. No NETBEUI etc.
Yes?

"Interrogative" a écrit dans le message de news:
...

"Castor" wrote in message
...

"Interrogative" a écrit dans le message de
news: ...

"Castor" wrote in message
...

"Interrogative" a écrit dans le message de
news: ...

"Castor" wrote in message
...
Hello,

I've TrendNet PCMCIA WiFi adapters in 2 systems to connect in 802.11g
to an AP/Router SMC2804WBR.
For weeks now, I'm facing a recurrent problem when starting the WiFi
connection on each system . The radio connection is well detected
but it can takes minutes to hours to establish the final IP
connection either in fixed IP or in DHCP IP. ( it's looping in
"Waiting for Network").

When connection is successful, after, it works fine with good signal
and speed.

It's not a question of signal strengh or quality because NetStumbler
is detecting a very good radio connection.

I went through the forums and find many persons pointing the same
problem and situation with SP2, I installed the correction
"WinsockXPFix.exe" proposed by MS, but it doesn't solve my problem.

My guess is that's related to the new way of processing WiFi which
arrived with SP2 ... I discussed with TRENDNET TechSupport and they
don't see any solution ...

Does somebody has new ideas and can help me solving this problem?


You say you use Netstumbler but to the best of my knowledge it doesn't
pick up cloaked networks and that is exactly what you may be
experiencing - a cloaked network on the same channel, nearby.
*** As far as I've experienced there are no other network broadcasting
around ... It works fine with my old Wifi 802.11b ELSA adapters ...


Try setting the channel to something other than what you currently use
and see if that helps.
*** Changing channels number doesn't change the result ...

You could also be having a problem with firewalls. Take them all
offline and see what happens.
*** With or without firewalls on it's the same...



***As I wrote in my initial message , after a waiting time looping on
"Waiting for network" it connects well and it can work for hours ...

****It's really a problem of establishing the connection after
activating it ...

So, ... Thanks for your interest in my problem ..


If that is the case, I would say you have signal attenuation of some
sort, then. My next suggestion is a signal booster/repeater somewhere
between the two. I get very occasionally, about 30 seconds of interval
for the laptop's external USB wi-fi Nic to attach to exactly the same
make and model one on this desktop machine. The laptop is at the other
end of the house with 3 walls in between which encompass the bathroom,
laundry (which also has the freezer in it) and kitchen with all the
usual kitchen appliances and volumes of metal there. Normally I get top
signal strength after that but penetrating all those things causes an
occasional lapse.

The way to test that thought is to put your two wi-fi machines in the
same room and see if you can repeat the performance they normally do. If
you get instant access, your problem will be helped or solved by a
repeater.


I did run tests with all the machines in the same room at a couple of
meters far from the AP/Router and it gave the result: very long waiting
time to connect ...
So, ...



Get HiJackThis and run a scan and save them and post them here. You said
you are manually assigning IPs and getting the same results. From all your
tests, all I can think is SOMETHING is starting at that time that is
causing this. I assume there is nothing other than TCP/IP in use. No
NETBEUI etc. Yes?

IP assignment: Yes, It's the same manually assigning or getting IP from
AP/router DHCP ...

Protocols: I have also Netlink IPX/SPX/Netbios and NetBios NWlink .
I need IPX/SPX because I have a network printer which work only in IPX ...

I've an old WiFi PCMCIA ELSA MC-11 (802.11b) adapter, and it works fine in
the same situation ...