K
Ken K
The day at Starbucks, which I think was Tuesday, I found the connectionChuck said:Chuck wrote:
Hi, Chuck.See post below...
Chuck wrote:
<SNIP>
Thank you for responding, Chuck. I don't think that the Avila Market
has any grudges against their clients--you are correct.
WRT other hotspots, I occasionally use the ones at Starbucks without any
problem. WRT Avila Market, I am told that I am one of 2-3 people who
have difficulty but that many others have none. One day I spent a half
hour with a bright fellow who works there and he was surprised that I
was unable to connect. We tried a direct connection to circumvent any
problems with wireless but that did not change anything. There is a
roving IT company whom they call when there are problems but they have
had no problems (other than me) so they have not called the IT people.
I do now know if this router requires authentication. I assume I would
be presented with a request for name and password? I have been told
that there is not a need for signing up with their website nor for
entering any name or password.
I will try some other websites. I have been unable to contact msn.com,
msnbc.com, cingular.com, etc.
When I have done this, I will post it. It will not be before tomorrow.
Will you continue to monitor this thread or should I leave a note on
your blog? I left my personal email address there today.
Thanks for your work so far on this puzzling problem.
Ken
Ken,
I help here to keep up with the issues that I may deal with in person later.
Your situation is intriguing, and I suspect that I will end up learning as much
as you do.
If you post in this thread, I'll see it. Just reply when you're ready.
Since you say that you did get help (unsuccessfully) from a local expert, I'm
thinking less and less that the problem might be with the hotspot. If you find
it convenient to sometime visit the other hotspot, an "ipconfig /all" log, along
with the results from the 4 way test for a couple websites, will make a good set
of comparative diagnostics.
When you uninstalled ZA, did you get instructions from ZoneLabs?
Chuck,
Here is followup from the 5/10 post. Basically, I updated the drivers
for the Intel 2516 wireless card adn I am back to where I was before:
everything works except the market, although I am able to ping the
router at Avila Market. Here is some info...
I decided yesterday to check the driver for the Intel wireless card and it was one or two versions behind, so I downloaded the driver and in stalled it. I am now back to where I was before: I was able to log onto Starbucks t-mobile hotspot with no problem but still had difficulty with the Avila Market. Following are the various files.
At Starbucks my reception remained at 11 Mbps all the time, as opposed to the day before when it varied down to 1 Mbps:
Windows IP Configuration
Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cust.hotspot.t-mobile.com
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-13-D3-AF-6C-8E
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : cust.hotspot.t-mobile.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG Network Connection
Physical Address. . . . . . . . . : 00-13-CE-C8-96-59
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.253.100.113
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . : 10.253.100.97
DHCP Server . . . . . . . . . . . : 10.253.100.97
DNS Servers . . . . . . . . . . . : 66.94.9.120
66.94.25.120
Lease Obtained. . . . . . . . . . : Wednesday, May 10, 2006 6:53:49 PM
Lease Expires . . . . . . . . . . : Wednesday, May 10, 2006 7:08:49 PM
Ping to DNS:
Pinging 66.94.9.120 with 32 bytes of data:
Reply from 66.94.9.120: bytes=32 time=63ms TTL=249
Reply from 66.94.9.120: bytes=32 time=61ms TTL=249
Reply from 66.94.9.120: bytes=32 time=61ms TTL=249
Reply from 66.94.9.120: bytes=32 time=62ms TTL=249
Ping statistics for 66.94.9.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 63ms, Average = 61ms
Ping to yahoo:
Pinging www.yahoo.akadns.net [66.94.230.50] with 32 bytes of data:
Reply from 66.94.230.50: bytes=32 time=68ms TTL=52
Reply from 66.94.230.50: bytes=32 time=81ms TTL=52
Reply from 66.94.230.50: bytes=32 time=82ms TTL=52
Reply from 66.94.230.50: bytes=32 time=97ms TTL=51
Ping statistics for 66.94.230.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 97ms, Average = 82ms
Ping to yahoo using their IP address:
Pinging 66.94.230.33 with 32 bytes of data:
Reply from 66.94.230.33: bytes=32 time=172ms TTL=51
Reply from 66.94.230.33: bytes=32 time=140ms TTL=51
Reply from 66.94.230.33: bytes=32 time=149ms TTL=51
Reply from 66.94.230.33: bytes=32 time=67ms TTL=51
Ping statistics for 66.94.230.33:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 172ms, Average = 132ms
Next, I drove over to the Avila Market. I was able to connect to the router and ping the gateway but that was all, as the following shows.
IPCONFIG
Windows IP Configuration
Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-13-D3-AF-6C-8E
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2915ABG Network Connection
Physical Address. . . . . . . . . : 00-13-CE-C8-96-59
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 24.205.224.35
64.214.48.27
Lease Obtained. . . . . . . . . . : Tuesday, May 09, 2006 7:29:26 AM
Lease Expires . . . . . . . . . . : Wednesday, May 10, 2006 7:29:26 AM
Ping to gateway:
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=150
Reply from 192.168.1.1: bytes=32 time=1ms TTL=150
Reply from 192.168.1.1: bytes=32 time=1ms TTL=150
Reply from 192.168.1.1: bytes=32 time=1ms TTL=150
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 = 1ms, Average = 1ms
Ping to yahoo:
Pinging 66.94.230.33 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 66.94.230.33:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Ping to DNS:
Pinging 64.214.48.27 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 66.94.230.33:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Ping to DNS
Pinging 24.205.224.35 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 66.94.230.33:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
So what thoughts do you have?????
Thanks
Ken
Ken,
I think we need to start by separating different issues:
# WiFi Connectivity - authentication and encryption issues.
# Bandwidth and stability - ping packet loss, and varying throughput problems.
# Network connectivity - ability to access Internet resources when connected.
I haven't written any, or identified any useful third party, articles on WiFi
authentication and encryption issues. But there are a few issues which I have
in mind, some of which I've touched on briefly with you. I'll write, with my
thoughts, later today.
I'll ask you to read some of my articles about WiFi problems in general, though.
Some of the items won't directly apply to you (you're not setting up the WiFi
router for instance), but they may contain insight.
<http://nitecruzr.blogspot.com/2005/11/setting-up-wifi-lan.html>
http://nitecruzr.blogspot.com/2005/11/setting-up-wifi-lan.html
<http://nitecruzr.blogspot.com/2005/10/wifi-will-never-be-as-fast-as-ethernet.html>
http://nitecruzr.blogspot.com/2005/10/wifi-will-never-be-as-fast-as-ethernet.html
<http://nitecruzr.blogspot.com/2006/05/you-have-to-share-wifi-bandwidth.html>
http://nitecruzr.blogspot.com/2006/05/you-have-to-share-wifi-bandwidth.html
I'm going to go thru your diagnostics later this morning, you have excellent
diagnostic skills (is that a side effect of Radiology maybe). I wish half the
folks asking for help here were half as thorough as you are. Maybe you'll
appreciate my articles, given your attention to detail. I'll bet there are a
couple explanations in there that may help you.
We are down in Newport today visiting our kids in college for the
weekend, so time will be limited. I will read as I am able to. Let me
know if the diagnostics I did give you any clues. We are off to England
for a couple of weeks late June and I would hate to schlep my laptop if
I am likely to have connectivity problems!
Thanks
Ken
Ken,
Having looked at your results from T-Mobile / Starbucks, it would appear that
your laptop is not having connectivity problems, or at least any that are its
own fault. The T-Mobile setup is a good baseline, and it looks good there.
Now WiFi connectivity is a complex subject. I've just begun to touch upon it in
my articles (linked above). Those articles describe the problems from a
domestic LAN viewpoint, ie your LAN where you control the LAN itself, and the
Internet service (as much as any customer can control the Internet service).
There are things that you can't control, as a domestic WiFi LAN owner.
# Noise on the channel (analogue interference).
# Neighbors sharing the WiFi spectrum (digital interference).
When you use a public hotspot, you are still subject to those problems. You
have 3 additional problems.
# Internet service used by the hotspot.
# Other customers at the hotspot (digital interference).
# Authentication / encryption used by the hotspot, to control the customers, and
to keep the customers secure.
These issues all apply after you are connected to the hotspot. Connection is
another issue. And authentication (do we allow you to connect) / encryption
(how we keep your data secure between you and the hotspot) is a problem.
# WEP, the original standard for WiFi security, only provided encryption, with a
static encryption key. The hackers figured out how to break the key, so WEP has
been dismissed for security.
# WPA / WPA2 has several versions of authentication and encryption. You will
probably use the simplest: WPA-PSK with TKIP. PSK is a pre-shared key, similar
to the key used in WEP, but more complex. TKIP is an encryption protocol which
starts off using the pre-shared key, but changes the encryption key regularly,
which keeps hackers from breaking the key.
# At most big hotspot chains, like T-Mobile, they have dismissed using WPA
because it's a pain in the @ss to setup. If you setup a home LAN, you will use
it, because you control the LAN. But how can you do that, if you don't control
or even meet the customers and their computers? And not everybody with a laptop
at Starbucks is capable of setting up a WPA client, without help.
With most hotspot chains, the hotspot itself will be open. You connect to the
hotspot, THEN you authenticate using your credit card (or maybe a token provided
by the store running the hotspot).
Obviously, you got connected to T-Mobile, since you provided ping diagnostics
from www.yahoo.com. So you have a baseline:
# Your laptop IS capable of connecting.
# YOU are capable of dealing with hotspot connection procedures.
The latter two issues are not always not certain, so it's good to get them out
of the way. With that in mind, you should be safe schlepping the laptop on your
trip.
Now, please clarify your earlier statement:
Was the day before at Starbucks too? Have you ever connected at the AvilaAt Starbucks my reception remained at 11 Mbps all the time, as opposed to the
day before when it varied down to 1 Mbps.
Market?
varied between 11Mbps down to 1 Mbps. It was curious. I went back on
Wednesday, sat in the same spot, and there was no problem, so it may
have been a problem with their wireless that day.
WRT to the Avila Market, the best that I have done is to have been able
to ping their router after I had been assigned an IP address, but I have
never been able to get online. I will probably be purchasing another
laptop in the not-too-distant future (my wife has wireless envy) and I
will see if I am able to connect with hers, but that will be a month or two.
Thanks
Ken