I have setup a secure wireless network which works very well except for two laptops running Ubuntu 10.10 that can't access the Internet via a browser at the same time. They can both ping sites, wget sites, use skype but when using a browser the page never loads (in Firefox the status bar just sits there saying "Connecting" until it times out.)
Here is what we have tried so far (nothing has fixed this issue):
- OpenDNS
- Restart networking services
- Using wired connection rather than wireless
- Removing all other nodes from the network except the two machines that have this issue
- Swapped out the router
- Factory reset the router
- Reformatted one of the machines and re-installed Ubuntu 10.10
Other things that we have checked:
- The two machines can connect simultaneously without any issues to other wireless networks in different locations (say in an Internet Cafe or another office)
- The two machines have unique IP addresses
- The two machines have unique MAC addresses
- The two machines can communicate on the network using Skype, wget, ping etc
- We are not using a proxy on either machine
FYI: I have attached output from wireshark. For the test we turned both machines on and pointed them both to the same website. The content loaded on one and not the other. Here is the output from wireshark- (speedyshare.com/files/26228631/machine_output_1 && speedyshare.com/files/26229335/machine_output_2). As you can see the first one worked, the second one didn't.
I don't fully understand the output and would appreciate if someone could shed some light on what might be causing this and how we can fix it!
Many thanks!
Darren
Looking at your traces, the two machines are trying to connect to two different endpoints. It looks like you are trying to connect to test.org.uk:
Machine 1
Connection results: successful transaction (with a 301 Moved result)
Machine 2
Connection results: the SYN request is ignored; no TCP connection is made
Suggestions
I'd say try connecting to these servers using their IP numbers instead of their DNS names.
By the way, I'm not sure that the other non-TCP traffic would be relevant...
My guess as to the culprit? The test server test.org.uk combined with the NAT gateway: test.org.uk might just be recognizing both machines as coming from the same source (the NAT gateway). But that doesn't solve the problem posed originally - if your problems go beyond just test.org.uk. Try another site.