I am totally lost, because my situation doesn't make sense. Here's a summary of all the points: 1) I connect through a Freecom DataTank, which is a Wireless Access Point and a switch in one. It's not setup as a router and services like DNS, DHCP are turned off because they are handled by the adsl modem. 2) Wired everything works great. 3) Wireless is a whole different story and confuses the hell out of me: a) I am connected to the AP and the network icon in the system tray indicates that I have an internet connection. b) However, I can only access the local network. Anything that connects to the outside world is just sitting there and waiting. c) Another laptop we have works just fine. The fact that wired works and wireless only works for the local network to me makes no sense. You would expect that if wireless can connect, it will have the same type of connection as wired. I hope someone can give me a clue.

Hi Michiel, I would like to confirm the following information with you: 1. What is the mode of the Freecom DataTank device? 2. Does the Windows Vista machine directly obtain a public IP address from the ISP? Please export the Windows IP Configuration for further research. 3. Can the Windows Vista machine ping the Default Gateway (Wireless Access Point)? 4. Can the Windows Vista machine access the website http://www.msftncsi.com/ncsi.txt? Meanwhile, please install the latest firmware and check the result.

Hi Joson, Thanks for your reply. Here's the information you requested: 1. It's in switch mode. 2. There is a router between the datatank and my ISP. The router uses DHCP to assign IP addresses. 3. Yes, it can. In fact, it can ping anything in my local network and can reach other machines through RDP and other protocols. For some domains it can ping outside the network, but this is rare. 4. No, "Internet Explorer cannot display the page." I have the latest firmware and drivers installed. Below is a dump of ipconfig /all. Note that this is with the wired connection also in there. That connection works fine (otherwise I wouldn't be able to post this right now), it's just the wireless that doesn't work for remote sites. Windows IP Configuration Host Name . . . . . . . . . . . . : Michiel-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Peer-Peer IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : vanotegem.local Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : vanotegem.local Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection Physical Address. . . . . . . . . : 00-1C-BF-2C-5F-66 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::6c6a:48c9:a0ac:6e6a%9(Preferred) IPv4 Address. . . . . . . . . . . : 10.0.0.200(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, May 01, 2008 8:57:58 PM Lease Expires . . . . . . . . . . : Thursday, May 01, 2008 11:15:13 PM Default Gateway . . . . . . . . . : 10.0.0.138 DHCP Server . . . . . . . . . . . : 10.0.0.138 DNS Servers . . . . . . . . . . . : 10.0.0.138 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : vanotegem.local Description . . . . . . . . . . . : Intel(R) 82566MM Gigabit Network Connection Physical Address. . . . . . . . . : 00-16-D3-CE-3D-10 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::751b:b730:86f7:89d4%8(Preferred) IPv4 Address. . . . . . . . . . . : 10.0.0.199(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, May 01, 2008 8:51:59 PM Lease Expires . . . . . . . . . . : Thursday, May 01, 2008 11:16:40 PM Default Gateway . . . . . . . . . : 10.0.0.138 DHCP Server . . . . . . . . . . . : 10.0.0.138 DNS Servers . . . . . . . . . . . : 10.0.0.138 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{4BD3CB43-5D44-4C09-8F9B-784DC5320DAC} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 9: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : vanotegem.local Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{E3614816-24DF-4817-86A8-BCC2787FDE19} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 16: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:05c7:a2ca:3445:b523:ada2:4980(Preferred) Link-local IPv6 Address . . . . . : fe80::3445:b523:ada2:4980%21(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled

Hi Michiel, Can you also send the output of "route print" command? Thanks.

Hi Yenely, Here is the route print output. 10.0.0.150 is the wireless interface, 10.0.0.151 the wired one. Thanks. ===========================================================================Interface List 9 ...00 1c bf 2c 5f 66 ...... Intel(R) PRO/Wireless 3945ABG Network Connection 8 ...00 16 d3 ce 3d 10 ...... Intel(R) 82566MM Gigabit Network Connection 1 ........................... Software Loopback Interface 115 ...00 00 00 00 00 00 00 e0 isatap.{4BD3CB43-5D44-4C09-8F9B-784DC5320DAC}20 ...00 00 00 00 00 00 00 e0 isatap.vanotegem.local16 ...00 00 00 00 00 00 00 e0 isatap.{E3614816-24DF-4817-86A8-BCC2787FDE19}19 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface=========================================================================== IPv4 Route Table===========================================================================Active Routes:Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.0.0.138 10.0.0.151 20 0.0.0.0 0.0.0.0 10.0.0.138 10.0.0.150 30 10.0.0.0 255.255.255.0 On-link 10.0.0.151 276 10.0.0.0 255.255.255.0 On-link 10.0.0.150 286 10.0.0.150 255.255.255.255 On-link 10.0.0.150 286 10.0.0.151 255.255.255.255 On-link 10.0.0.151 276 10.0.0.255 255.255.255.255 On-link 10.0.0.151 276 10.0.0.255 255.255.255.255 On-link 10.0.0.150 286 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 169.254.0.0 255.255.0.0 On-link 10.0.0.151 30 169.254.255.255 255.255.255.255 On-link 10.0.0.151 276 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 10.0.0.151 276 224.0.0.0 240.0.0.0 On-link 10.0.0.150 286 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 10.0.0.151 276 255.255.255.255 255.255.255.255 On-link 10.0.0.150 286===========================================================================Persistent Routes: None IPv6 Route Table===========================================================================Active Routes:If Metric Network Destination Gateway19 18 ::/0 On-link 1 306 ::1/128 On-link19 18 2001::/32 On-link19 266 2001:05c7:a2ca:3445:b523:ada2:4980/128 On-link 8 276 fe80::/64 On-link 9 286 fe80::/64 On-link19 266 fe80::/64 On-link19 266 fe80::3445:b523:ada2:4980/128 On-link 9 286 fe80::6c6a:48c9:a0ac:6e6a/128 On-link 8 276 fe80::751b:b730:86f7:89d4/128 On-link 1 306 ff00::/8 On-link19 266 ff00::/8 On-link 8 276 ff00::/8 On-link 9 286 ff00::/8 On-link===========================================================================Persistent Routes: None

Itseems that you have valid IP address and valid routes. Itmay be a firewall or ipsec or wireless issue. Can you disable the firewall engine and see that it helps. command is "net stop bfe" (it will both stop ipsec and firewall) While you are trying to reach external pages can you do a networkcapture and see that your TCP packets are going out? http://www.microsoft.com/downloads/details.aspx?FamilyID=18b1d59d-f4d8-4213-8d17-2f6dde7d7aac&displaylang=en Thanks.

Hi Yenel, thanks for getting back to me. The Network Monitor isinteresting to watch, although I still have no clue as to the cause (let alone the solution). NM showsthat I actually get an HTTP 200 OK response with some payload and several packages with payload after that. Problem is,they don't amountto thefull page, so I guess IE is waiting for more packages. Last I see is another HTTP GET from my machine, followed by a TCP acknowledgement from the remote host. After that nothing. Stopping BFE didn't help.

Thanks for your response. It helped me to understand the issue more. It seems that your machine as a host doesnt have any problem. Remote host is not sending data or some routers in the middle (maybe your gateway) is dropping packets.In the past we have seenrotures are dropping packets because of Window Scaling feature in TCP. Disable the Window Scaling and see that if it helps. To disable TCP Windows Scaling In Vista: Note: This command MUST be run as administrator Locate the Command Prompt icon/executable file under Start->Accessories Right-click on the icon and select "Run as administrator" Type: netsh interface tcp set global autotuninglevel=disabled To verify the settings on the workstation, use the command: netsh interface tcp show global The results of this command should be something like this: TCP Global Parameters _____________________ Receive-Side Scaling State : enabled Chimney Offload State : enabled Receive Window Auto-Tuning Level : disabled Add-On Congestion Control Provider : ctcp ECN Capability : disabled RFC 1323 Timestamps : disabled

Yenel, Whatever it was, a change in my network configuration seems to have done the job. After switching the Freecom device from Switch mode to Router mode everything works (apart from totally unrelated issues that already have been attributed to the Freecom device). Thanks for the help.