T61/P WiFi Connection Delay

Operating System, Common Application & ThinkPad Utilities Questions...
Post Reply
Message
Author
Harryc
Moderator Emeritus
Moderator Emeritus
Posts: 13228
Joined: Thu Apr 12, 2007 8:23 am
Location: Upstate New York

T61/P WiFi Connection Delay

#1 Post by Harryc » Tue Jan 22, 2008 10:08 am

I am scratching my head on a problem under XP network connection management. It takes 2 to 3 minutes for the WiFi adapter in my T61P to acquire an IP address after I'm booted to the desktop. This is a fresh install and it worked fine under Vista. Below are the relevent settings, and I can't see anything obvious. Can you? (I x'd out the Mac address). I haven't tried any other drivers beside the IBM/Atheros 5.3.0.85. The adapter is an IBM 11a/b/g Atheros card and I don't have this issue on any other XP laptops. I am running DHCP and my wireless router in a Linksys/Cisco WRT54G. I do not use access connections, windows manages the connection. I see DHCPLeaseExpires in 24 hours, could that be it?

[00000001] 11a/b/g Wireless LAN Mini PCI Express Adapter (PASSED)
Caption = [00000001] 11a/b/g Wireless LAN Mini PCI Express Adapter
DatabasePath = %SystemRoot%\System32\drivers\etc
DefaultIPGateway = 192.168.1.1(Same Subnet) (PASSED)
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=60ms TTL=60
Reply from 192.168.1.1: bytes=32 time=4ms TTL=4
Reply from 192.168.1.1: bytes=32 time=2ms TTL=2
Reply from 192.168.1.1: bytes=32 time=19ms TTL=19
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 60ms, Average = 21ms
DefaultTTL = 128
Description = 11a/b/g Wireless LAN Mini PCI Express Adapter - Packet Scheduler Miniport
DHCPEnabled = TRUE
DHCPLeaseExpires = 7:04:44 AM 1/23/2008
DHCPLeaseObtained = 7:04:44 AM 1/22/2008
DHCPServer = 192.168.1.1 (PASSED)
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=2ms TTL=2
Reply from 192.168.1.1: bytes=32 time=81ms TTL=81
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=2ms TTL=2
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 81ms, Average = 21ms
DNSEnabledForWINSResolution = FALSE
DNSHostName = LENOVO-D58276A3
DNSServerSearchOrder (PASSED)
68.237.161.12 (PASSED)
Pinging 68.237.161.12 with 32 bytes of data:
Reply from 68.237.161.12: bytes=32 time=27ms TTL=27
Reply from 68.237.161.12: bytes=32 time=61ms TTL=61
Reply from 68.237.161.12: bytes=32 time=139ms TTL=139
Reply from 68.237.161.12: bytes=32 time=27ms TTL=27
Ping statistics for 68.237.161.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 139ms, Average = 63ms
71.250.0.12 (PASSED)
Pinging 71.250.0.12 with 32 bytes of data:
Reply from 71.250.0.12: bytes=32 time=27ms TTL=27
Reply from 71.250.0.12: bytes=32 time=27ms TTL=27
Reply from 71.250.0.12: bytes=32 time=30ms TTL=30
Reply from 71.250.0.12: bytes=32 time=60ms TTL=60
Ping statistics for 71.250.0.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 60ms, Average = 36ms
DomainDNSRegistrationEnabled = FALSE
FullDNSRegistrationEnabled = TRUE
GatewayCostMetric = 25
Index = 1
IPAddress = 192.168.1.110 (PASSED)
Pinging 192.168.1.110 with 32 bytes of data:
Reply from 192.168.1.110: bytes=32 time<1ms TTL=0
Reply from 192.168.1.110: bytes=32 time<1ms TTL=0
Reply from 192.168.1.110: bytes=32 time<1ms TTL=0
Reply from 192.168.1.110: bytes=32 time<1ms TTL=0
Ping statistics for 192.168.1.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
IPConnectionMetric = 25
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.255.0
IPXEnabled = FALSE
MACAddress = xx:xx:xx:xx:xx:xx
PMTUBHDetectEnabled = FALSE
PMTUDiscoveryEnabled = TRUE
ServiceName = AR5211
SettingID = {D4229A29-EEED-4BE8-8A78-3919952A8DD3}
TcpipNetbiosOptions = 0
TcpWindowSize = 64240
WINSEnableLMHostsLookup = TRUE

jdhurst
Admin
Admin
Posts: 5831
Joined: Thu Apr 29, 2004 6:49 am
Location: Toronto, Canada

Re: T61/P WiFi Connection Delay

#2 Post by jdhurst » Tue Jan 22, 2008 1:30 pm

Harryc wrote:<snip>
1. Below are the relevent settings, and I can't see anything obvious. Can you?
2. I see DHCPLeaseExpires in 24 hours, could that be it?
3. DNSHostName = LENOVO-D58276A3
4. WINSEnableLMHostsLookup = TRUE
1. No
2. My leases expire in a week, not a day, but I do not think this is the reason.
3. Why this? DNS host should be a local DNS provider, or a server if you are working behind a server.
4. Did you check your hosts file for strange entries?

... JDH

Harryc
Moderator Emeritus
Moderator Emeritus
Posts: 13228
Joined: Thu Apr 12, 2007 8:23 am
Location: Upstate New York

#3 Post by Harryc » Tue Jan 22, 2008 2:46 pm

JDH, thanks for the reply. The only entry in my hosts file is;
127.0.0.1 localhost

My ISP does DNS using (2) seperate servers out on their Network. I know the IP addresses of those servers. Where would I find and change 'DNSHostName = LENOVO-D58276A3' on my machine, and what would I change it to? Just the DNS servers IP address? I have no idea what the hostname would be for their servers. This is something I've never had to mess with in 30 years of computing. As a side note I installed 'Access Connections' and the problem went away. It's not my favorite tool but it came in handy this time.

Edit: I see LENOVO-D58276A3 in 'system properties' under the 'computer name' field. This must get assigned to the DNS hostname automatically. I've never messed with it and it never caused this problem.

jdhurst
Admin
Admin
Posts: 5831
Joined: Thu Apr 29, 2004 6:49 am
Location: Toronto, Canada

#4 Post by jdhurst » Tue Jan 22, 2008 5:21 pm

I haven't seen my computer name associated with DNS, but then maybe I haven't looked in the right place. In any event, I rename my machines on birth, and I forgot about the Lenovo name.

Let's come at this a different way. So long as you are using DHCP and authomatic DNS, then that should not be a problem, and so nothing I identified was a cause.

I don't know, as your setup looks fine.
... JDH

Post Reply
  • Similar Topics
    Replies
    Views
    Last post

Return to “Windows OS (Versions prior to Windows 7)”

Who is online

Users browsing this forum: No registered users and 3 guests