Hotel Wi-Fi woes

[BrowneIssue]

I have an intermittent fault with the WiFi in the hotel I'm in.

My WiFi card has a good, continuous signal from the router. Yet most of the time I can't get a web page to come up. If I try to go to the login page on the wifi router, half the time I can't even get that to come up.
Sometimes the browser will time out. Most of the time it just sits there with a spinning logo - seemingly for ever (certainly for over an hour). A web page may come up in little bits until it finally stops being added to.

The WiFi card shows traffic going up & down for a few seconds, then nothing. But it also show "Connected" consistently.

This setup has worked fine in half a dozen other locations this past few months.

Comms ain't my thing so I don't really know where to start. Any ideas? Another router on the same channel? A 'noisy' suppressor on a 'fridge?

Random info
Router: Prestige 660HW-T1 on 192.168.1.1
Laptop WiFI: 3COM 54Mbps 11g PC Card on 192.168.1.35

C:\Windows\Desktop>tracert forums.contractoruk.com

Tracing route to forums.contractoruk.com [89.16.161.127]
over a maximum of 30 hops:

1 13 ms <10 ms 42 ms 192.168.1.1
2 28 ms 27 ms 28 ms 89.104.226.1.reverse.converged.co.uk [89.104.226.1]
3 28 ms 27 ms 28 ms 195.72.128.129
4 28 ms 27 ms 14 ms 194.153.169.105
5 27 ms 28 ms 27 ms gi4-12.cr01.sov.bytemark.co.uk [194.153.169.205]
6 28 ms 27 ms 28 ms e0.statler.bytemark.co.uk [80.68.80.110]
7 27 ms 42 ms 27 ms gi0-23.agg2.man.bytemark.co.uk [89.16.160.46]
8 28 ms 27 ms 28 ms cukmain.dh.bytemark.co.uk [89.16.161.127]

Trace complete.

C:\Windows\Desktop>tracert forums.contractoruk.com

Tracing route to forums.contractoruk.com [89.16.161.127]
over a maximum of 30 hops:

1 <10 ms <10 ms 41 ms 192.168.1.1
2 27 ms 27 ms 28 ms 89.104.226.1.reverse.converged.co.uk [89.104.226.1]
3 28 ms 14 ms 27 ms 195.72.128.129
4 14 ms 28 ms 27 ms 194.153.169.105
5 27 ms 14 ms 28 ms gi4-12.cr01.sov.bytemark.co.uk [194.153.169.205]
6 41 ms 28 ms 27 ms e0.statler.bytemark.co.uk [80.68.80.110]
7 28 ms 27 ms 41 ms gi0-23.agg2.man.bytemark.co.uk [89.16.160.46]
8 41 ms 28 ms 27 ms cukmain.dh.bytemark.co.uk [89.16.161.127]

Trace complete.

C:\Windows\Desktop>ping -n 40 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=13ms TTL=254
Reply from 192.168.1.1: bytes=32 time=14ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=14ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=124ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=138ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.1:
Packets: Sent = 40, Received = 14, Lost = 26 (65% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 138ms, Average = 7ms

C:\Windows\Desktop>ping -n 40 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=27ms TTL=254
Reply from 192.168.1.1: bytes=32 time=14ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=14ms TTL=254
Reply from 192.168.1.1: bytes=32 time=13ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=13ms TTL=254
Reply from 192.168.1.1: bytes=32 time=234ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=14ms TTL=254
Reply from 192.168.1.1: bytes=32 time=14ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=13ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=261ms TTL=254
Reply from 192.168.1.1: bytes=32 time=13ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=14ms TTL=254
Reply from 192.168.1.1: bytes=32 time<10ms TTL=254
Reply from 192.168.1.1: bytes=32 time=13ms TTL=254

Ping statistics for 192.168.1.1:
Packets: Sent = 40, Received = 27, Lost = 13 (32% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 261ms, Average = 16ms

C:\Windows\Desktop>

C:\Windows\Desktop>tracert forums.contractoruk.com
Unable to resolve target system name forums.contractoruk.com.

C:\Windows\Desktop>tracert forums.contractoruk.com

Tracing route to forums.contractoruk.com [89.16.161.127]
over a maximum of 30 hops:

1 14 ms <10 ms 14 ms 192.168.1.1
2 68 ms 14 ms 137 ms 89.104.226.1.reverse.converged.co.uk [89.104.226.1]
3 27 ms 14 ms 14 ms 195.72.128.129
4 27 ms 27 ms 28 ms 194.153.169.105
5 * * * Request timed out.
6 * * * Request timed out.
7 * * 27 ms gi0-23.agg2.man.bytemark.co.uk [89.16.160.46]
8 192 ms 69 ms 137 ms cukmain.dh.bytemark.co.uk [89.16.161.127]

Trace complete.

C:\Windows\Desktop>tracert forums.contractoruk.com
Unable to resolve target system name forums.contractoruk.com.

C:\Windows\Desktop>ipconfig

Windows IP Configuration

0 Ethernet adapter :

IP Address. . . . . . . . . : 192.168.1.35
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1

1 Ethernet adapter :

Media Status. . . . . . . . : Disconnected
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :

2 Ethernet adapter :

Media Status. . . . . . . . : Disconnected
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :

3 Ethernet adapter :

IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :

C:\Windows\Desktop>tracert forums.contractoruk.com

Tracing route to forums.contractoruk.com [89.16.161.127]
over a maximum of 30 hops:

1 <10 ms <10 ms 27 ms 192.168.1.1
2 14 ms 27 ms 28 ms 89.104.226.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * 14 ms gi4-12.cr01.sov.bytemark.co.uk [194.153.169.205]
6 42 ms 41 ms 41 ms e0.statler.bytemark.co.uk [80.68.80.110]
7 27 ms 28 ms 54 ms gi0-23.agg2.man.bytemark.co.uk [89.16.160.46]
8 41 ms 41 ms 152 ms cukmain.dh.bytemark.co.uk [89.16.161.127]

Trace complete.

C:\Windows\Desktop>

[BrowneIssue]

Wi-Fi utility stats:

TX
Total packet: 16739
Single retries: 1912
Multiple retries: 2071

RX
Total packet: 64130
Duplicate frame: 162
Received beacons: 56671
Beacon loss: 7223

SInce I can watch the beacon loss go up (7248) I assume there is a clue (7260).

[KevinS]

Are you using 3Com software to manage the connection? If so, I would uninstall the 3Com utility and let Windows handle the WiFi connection. If not, then try installing some 3Com software and see how that handles.

I can't see it being the router as I have on of these Zyxel Prestige 660HW and I have yet to have an issue with the wireless..

[BrowneIssue]

Are you using 3Com software to manage the connection? If so, I would uninstall the 3Com utility and let Windows handle the WiFi connection. If not, then try installing some 3Com software and see how that handles.

I am at ClientCo now where the connection is rock solid, despite having a 12-18% signal strength.

I'm running Windows ME so I don't think Windows can handle the WiFi for itself, can it?

[KevinS]

I am at ClientCo now where the connection is rock solid, despite having a 12-18% signal strength.

I'm running Windows ME so I don't think Windows can handle the WiFi for itself, can it?

Windows ME??

No, it can't so there goes that option.. Try deleting the hotel WiFi entry and letting it 'rediscover' when you get back..

[ratewhore]

Move hotels.

HTH

RW

[NickFitz]

I am at ClientCo now where the connection is rock solid, despite having a 12-18% signal strength.

I'm running Windows ME so I don't think Windows can handle the WiFi for itself, can it?

Have you tried Linux? Maybe run it from a memory stick - that's supposed to be easy to set up.

<ducks>

[BrowneIssue]

Move hotels.

I have done.

Twice.

[BrowneIssue]

Have you tried Linux? Maybe run it from a memory stick - that's supposed to be easy to set up.

<ducks>

Cailin, may I borrow your paddy-whacker?

[BrowneIssue]

Windows ME??

No, it can't so there goes that option.. Try deleting the hotel WiFi entry and letting it 'rediscover' when you get back..

I did do that last night. I've had another go at doing so - no difference. Up and down like a <probably can't use that simile in this forum> up-and-downy thing.