Your assumption would be mine also, with the problem being that there are other people using the bandwidth also. There are many devices that operate at 2.4Ghz, such as baby monitors, microwave ovens, 802.11b&g, etc. etc.... another likely issue is that the pipe to the ISP is saturated, which would cause you to see an excellent signal, but slow speeds.
Try this.... open 2 command windows... START > RUN > type "CMD". Once you have those open, do an "IPCONFIG" in one, and note down the DEFAULT GATEWAY. In one window, type "PING 192.168.1.1 -t" (sub the number you wrote down in there, if it isn't 192.168.1.1). In the other window, type "PING google.com -t". This will run a CONTINUOUS ping to both the gateway router at the hotel, and the google.com server. You will want to keep an eye on the response times to see if they change over a short period of time like your speed changes....
Quote:
U:\>ping google.com -t
Pinging google.com [64.233.187.99] with 32 bytes of data:
Reply from 64.233.187.99: bytes=32 time=39ms TTL=238
Reply from 64.233.187.99: bytes=32 time=41ms TTL=238
Reply from 64.233.187.99: bytes=32 time=52ms TTL=238
Reply from 64.233.187.99: bytes=32 time=42ms TTL=238
Reply from 64.233.187.99: bytes=32 time=41ms TTL=238
Reply from 64.233.187.99: bytes=32 time=46ms TTL=238
Reply from 64.233.187.99: bytes=32 time=37ms TTL=238
Reply from 64.233.187.99: bytes=32 time=36ms TTL=238
Reply from 64.233.187.99: bytes=32 time=39ms TTL=238
Reply from 64.233.187.99: bytes=32 time=37ms TTL=238
Reply from 64.233.187.99: bytes=32 time=38ms TTL=238
Reply from 64.233.187.99: bytes=32 time=38ms TTL=238
Reply from 64.233.187.99: bytes=32 time=37ms TTL=238
Reply from 64.233.187.99: bytes=32 time=41ms TTL=238
|
As you can see here in this ping to google, the time is listed in Mili-seconds. You should see times of 1-3ms to the gateway, and times will vary to Google.
To stop the ping, click on one of the windows, and hit CTRL+C. Then click on the other window and do the same.