Laptop..... problems acquiring network address

  • Thread starter Thread starter goflynn
  • Start date Start date
G

goflynn

I'm having a problem with my new Trendnet 802.11g wireless router,
(TEW-432BRP) I have comcast cable and my laptop initially connects
fine to the router and I can surf the internet. After a period of
time approx 24 hours, I'll try connect again and my computer can
longer connect, it stalls stuck acquiring it's network address. If i
power cycle the router then everything works again. I just set up a
similar set up for my brother in his apartment with a D-link wireless
router and he is experiencing the same problems. Again when the
router is rebooted everything works fine. Am i missing some basic
router setting that would explain this behavior.. Is the security
settings I have chosen a possibility WPA2,PSK-TKIP. The DHCP lease is
multiple day .. I never had this problem with my previous netgear
router. I upgraded because it only had only WEP .

thanks in advance
 
Please post the text output of ipconfig /all when it is in the "no
connect" state. also-do you have the latest driver for your NIC and
the latest firmware for the router?

I'm having a problem with my new Trendnet 802.11g wireless router,
(TEW-432BRP) I have comcast cable and my laptop initially connects
fine to the router and I can surf the internet. After a period of
time approx 24 hours, I'll try connect again and my computer can
longer connect, it stalls stuck acquiring it's network address. If i
power cycle the router then everything works again. I just set up a
similar set up for my brother in his apartment with a D-link wireless
router and he is experiencing the same problems. Again when the
router is rebooted everything works fine. Am i missing some basic
router setting that would explain this behavior.. Is the security
settings I have chosen a possibility WPA2,PSK-TKIP. The DHCP lease is
multiple day .. I never had this problem with my previous netgear
router. I upgraded because it only had only WEP .

thanks in advance
Click to expand...
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
sorry for the delay I was waiting for it to fail again . Here are the
return values for ipconfig. What is the autoconfiguration IP address?
It looks like the subnet mask may be off and also that IP doesn't look
like one in range that is assigned by the router.


Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1390 WLAN
Mini-Card
Physical Address. . . . . . . . . : 00-1B-FC-10-D8-3D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.112.243
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

after power cycling the router I get
Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1390 WLAN
Mini-Card
Physical Address. . . . . . . . . : 00-1B-FC-10-D8-3D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Saturday, December 01,
2007 1:27:24 AM
Lease Expires . . . . . . . . . . : Saturday, December 08,
2007 1:27:24 AM
 
You didn't respond with the driver or firmware info.
I found
http://support.dell.com/support/dow...=1&vercnt=8&formatcnt=1&libid=5&fileid=187881
which has a critical update - and
http://support.dell.com/support/dow...-1&impid=-1&formatcnt=1&libid=5&fileid=202138

there may be more recent driver. you need to check the dell site.

can you please check the firmware on your router and on the vendor's
site to see if there is an update?
http://www.trendnet.com/downloads/info/tew-432brp.htm

sorry for the delay I was waiting for it to fail again . Here are the
return values for ipconfig. What is the autoconfiguration IP address?
It looks like the subnet mask may be off and also that IP doesn't look
like one in range that is assigned by the router.


Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1390 WLAN
Mini-Card
Physical Address. . . . . . . . . : 00-1B-FC-10-D8-3D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.112.243
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

after power cycling the router I get
Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Dell Wireless 1390 WLAN
Mini-Card
Physical Address. . . . . . . . . : 00-1B-FC-10-D8-3D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
Lease Obtained. . . . . . . . . . : Saturday, December 01,
2007 1:27:24 AM
Lease Expires . . . . . . . . . . : Saturday, December 08,
2007 1:27:24 AM
Click to expand...
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
The router firmware is up to date. My network driver is a little
confusing. Using the dell service tag there are no updates listed for
my system. The running driver version is 4.100.15.5 which seems to be
the most resent. I bought the system in May 2007. The Dells driver
info page you sent lists v.4.100.15.5 / 4.100.15.8, A14) My only
doubts is that the properties/driver date on my system is 10/12/2006
which is before the release date of the drivers you linked for me. I
don't know whether to trust the driver dates over the driver Version
information.
 
I'd set a restore point and try the latest drivers.

The router firmware is up to date. My network driver is a little
confusing. Using the dell service tag there are no updates listed for
my system. The running driver version is 4.100.15.5 which seems to be
the most resent. I bought the system in May 2007. The Dells driver
info page you sent lists v.4.100.15.5 / 4.100.15.8, A14) My only
doubts is that the properties/driver date on my system is 10/12/2006
which is before the release date of the drivers you linked for me. I
don't know whether to trust the driver dates over the driver Version
information.
Click to expand...
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Thanks Barb, I have updates my drivers with the latest from Dell .I
believe they were already current because I am not seeing any
changes with Date or version undwer properties for the driver. As a
temporary fix, we ended up changing the network from WPA2 to WPA. This
seem to have solved the problems..(we are 3 days in ) Is WPA2 more
troublesome in terms of compatibility? I almost feel the router was at
fault as we had three laptops running on the network, 2 windows XP , 1
linux, and all were experiencing the same problem. After power
cycling the router there is no problem connecting to the network but
after a period of time (+24 hours) the network is no longer working.
The network icon says we are attached but the ip address is not being
acquired by laptops per description above. Does this behavior ring any
bells for WPA2. I'm not happy settling for WPA if WPA2 is a superior
security protocol. I also feel a little beaten and I want to return
and try get the WPA2 going again once my roommates go away this
weekend. I still want to understand what's happening or if an
additional setting was omitted by me.

thanks
gearoid
 
WPA2 is more secure than WPA. I would agree that this could be a
router issue. If there is no firmware fix for the router available,
since you state it is a new router, I'd consider exchanging it for
one of the better known brands.

Thanks Barb, I have updates my drivers with the latest from Dell .I
believe they were already current because I am not seeing any
changes with Date or version undwer properties for the driver. As a
temporary fix, we ended up changing the network from WPA2 to WPA. This
seem to have solved the problems..(we are 3 days in ) Is WPA2 more
troublesome in terms of compatibility? I almost feel the router was at
fault as we had three laptops running on the network, 2 windows XP , 1
linux, and all were experiencing the same problem. After power
cycling the router there is no problem connecting to the network but
after a period of time (+24 hours) the network is no longer working.
The network icon says we are attached but the ip address is not being
acquired by laptops per description above. Does this behavior ring any
bells for WPA2. I'm not happy settling for WPA if WPA2 is a superior
security protocol. I also feel a little beaten and I want to return
and try get the WPA2 going again once my roommates go away this
weekend. I still want to understand what's happening or if an
additional setting was omitted by me.

thanks
gearoid
Click to expand...
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Thanks I'll report back if I make any further advances but as I say I
tried to set up my Brothers router which was a different DLINk brand
and i saw some similar behavior with that router. That said, I had
only one weekend to collect data on that routers behavior.
 
you never gave details on which D-Link router or what firmware it
was using. Need model #, hardware revision, and what firmware.

Thanks I'll report back if I make any further advances but as I say I
tried to set up my Brothers router which was a different DLINk brand
and i saw some similar behavior with that router. That said, I had
only one weekend to collect data on that routers behavior.
Click to expand...
--

Barb Bowman
MS Windows-MVP
http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
http://blogs.digitalmediaphile.com/barb/
 
Back
Top