I see many, many threads about this issue, but none quite like what I am experiencing. I am the de facto systems administrator for a small Windows 2003 AD network. I have recently started replacing our aging XP notebooks with new HP Windows 7 Pro 64 bit notebooks. I do not have any issues connecting to my internal AD domain inside the office nor do I have any issues access the internet through our ISA Server with the new computer. All computers are SP1 and fully up to date. No driver updates are available. The issue comes up, though inconsistantly, when I establish a WiFi or WWAN (Verizon air card) connection. I can make the connection, but it shows no internet access available. Restarting the device more often than not does not resolve the issue. The weird thing is that while I cannot browse the internet, I can VPN back into my network, at which point I have internet access. So obviously I DO have access to the internet, just not HTTP access until I connect back into my network. Windows Network Diagnostic turns up nothing. All of the computers are domain members. When I experience this on any of the computers I am setting up, prior to establishing a VPN connection I can netstat -n and see time_wait for the internal address of one of my network DCs, or other times for the public IP of my VPN connection. So it seems like my private domain info is getting stuck someplace and interfering with the Wifi and WWAN conectivity??? Any thoughts on this? Also, none of the XP SP3 computer experience anything like this issue. No GPOs in place that would cause this that I know of, but maybe something default that I am missing

Do you connect with both Ethernet and WIFI\Air Port? If so, you need to pay attention to the default gateway. Default Gateway Configuration for Multihomed Computers http://support.microsoft.com/kb/157025 TCP/IP Routing Basics for Windows NT http://support.microsoft.com/kb/140859Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I'll take a look and see if any of the info helps. A basic rundown of our network configuration: We use only ethernet to connect to our private network while we are physically in the office. Windows Active Directories network, Server 2003 R2, IPv4 DHCP, WINS, ISA Server 2006 firewall and proxy. There is a WPAD entry for proxy configuration. There are no statics entries on any of the network interfaces. When I ipconfig /all is see 0.0.0.0 assigned to non-connected interfaces. IPv6 has been disabled. I have had that disabled all along after I discovered leaving it enabled caused problems with VPN. When my associates are traveling they use their WiFi to connect to whatever available network they may need to connect to, or some users have Verizon air cards. They can then connect back into our private network via VPN through the ISA server. I currently only have one GPO that impacts the new Windows 7 computers, and all that does is deploy printers, so I don't think I have that to be concerned with This has never been an issue with our XP SP3 computers.

None of that info helped. Still consistant, issues with Wifi and WWAN. Connected to the wireless just fine, but no interent access. Diagnostic finds no problems. Search for new drivers yields nothing. I thought perhaps ISA Firewall Client was causing this issue, but even on systems that have not had the client installed yet the same issues is present. Sometimes disabling and reinabling Wifi helps, other times it does not. Sometimes just waiting 15 or 20 minutes after connecting to Wifi or WWAN helps, other times not. I have no control over the routers that my associates have to connect to since they are at hotels or customer sites, so if this is a 'router issue' there is nothing I can do there. From what I see on the web, 100s of people have this or similar issue with Windows 7. Makes me wish I had replaced my laptops a year ago when I could still get the custom downgrade to XP :(