Windows 2003 domain. Dell Optiplex Windows 7 Machines take a long time to allow Internet Access...up to an hour. You can use any network resources but there is NO INTERNET ACCESS under the Network Screen. I have 90 windows XP machines also on this network and they have no problem at all. Internet Access is immediately Available when the user logs in. We use an InstaGate Router as a Gateway. These are Wired 1gig connections to our Dell PowerConnect Switches. CA Etrust Antivirus isn't the issue since I turn it off and still have same issue.

Have you verified the TCP/IP settings on the Windows 7 computers in the first "hour". Are they consistant with that of other Windows XP systems? Have you checked the perimeter firewall/router logs to see if any traffic is coming from the Windows 7 systems outbound to the internet? If you would like, post the results of IPCONFIG /all from a Win 7 system experiencing this issue. Visit: anITKB.com, an IT Knowledge Base.

Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\shutson>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : BCMDRL1 Primary Dns Suffix . . . . . . . : mtc.mansion.rosewoodhotels.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : mtc.mansion.rosewoodhotels.local crescent.rosewoodhotels.com Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : mtc Description . . . . . . . . . . . : Intel(R) 82578DM Gigabit Network Connecti on Physical Address. . . . . . . . . : A4-BA-DB-F5-79-4A DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.2.95(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, September 15, 2010 4:05:36 AM Lease Expires . . . . . . . . . . : Tuesday, October 05, 2010 4:05:35 AM Default Gateway . . . . . . . . . : 192.168.2.1 DHCP Server . . . . . . . . . . . : 192.168.2.7 DNS Servers . . . . . . . . . . . : 192.168.2.7 192.168.2.8 Primary WINS Server . . . . . . . : 192.168.2.9 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.mtc: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : mtc Description . . . . . . . . . . . : Microsoft ISATAP Adapter 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 . . . . . . . . . . . : Microsoft 6to4 Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\shutson>

C:\Users\shutson>netsh interface ip show config Configuration for interface "Local Area Connection" DHCP enabled: Yes IP Address: 192.168.2.95 Subnet Prefix: 192.168.2.0/24 (mask 255.255.255.0) Default Gateway: 192.168.2.1 Gateway Metric: 0 InterfaceMetric: 10 DNS servers configured through DHCP: 192.168.2.7 192.168.2.8 Register with which suffix: Primary only WINS servers configured through DHCP: 192.168.2.9 Configuration for interface "Loopback Pseudo-Interface 1" DHCP enabled: No IP Address: 127.0.0.1 Subnet Prefix: 127.0.0.0/8 (mask 255.0.0.0) InterfaceMetric: 50 Statically Configured DNS Servers: None Register with which suffix: Primary only Statically Configured WINS Servers: None C:\Users\shutson>

I dont see anything out of the ordinary with regard to the IP settings. IN your statement, " NO INTERNET ACCESS under the Network Screen. ", just to verify, you do have access to internet resources, but you are simply concerned that the ICON and/or message in the Network Properties screen indicates that there is no connectivity? Visit: anITKB.com, an IT Knowledge Base.

We cannot connect to any Internet site , get the troubleshooting message.

Ok, this is going to be difficult to troubleshoot properly if you are using a web browser or control panel icons and messages to diagnose the issue. I would recommend that you focus on lower level networking protocols to validate connectivity and name resolution. During the time that you have no internet connectivity, you will need to verify if you have connectivity to the default gateway, remote host past the gateway, able to resolve host names using DNS, Access through your perimeter firewall, etc... Some tools that you can use to troubleshoot this: PING, TRACERT, ROUTE, NSLOOKUP Using PING to Test for Network Connectivity http://www.anitkb.com/2010/06/using-ping-to-test-for-network.html Ping and ICMP Error Messages http://www.anitkb.com/2010/06/ping-and-icmp-error-messages.html Using NSLOOKUP to Troubleshoot Common DNS Issues http://www.anitkb.com/2010/03/using-nslookup-to-troubleshoot-common.html Also, as I mentioned in my first post in this thread, check the internet router and/or firewall logs to validate if traffic is passing for those Win 7 clients. Visit: anITKB.com, an IT Knowledge Base.

Hi, Please check if you can access the Internet resources or websites when the network shows “NO INTERNET ACCESS”. Please check if you can access “http://www.msftncsi.com/ncsi.txt” in Internet Explorer. First, please go to run the built-in network troubleshooter. You can also try the following steps to troubleshoot the issue. 1. Boot the system to Safe Mode with networking and see if the issue persists. If not, please also boot to Clean Boot environment to determine the possible cause. 2. Update or reinstall the NIC driver and update the router’s firmware. 3. Refresh a new IP address ------------------------------------------ a. Click the Start Button, type "cmd" (without quotation marks), in the search result list, right click on Cmd.exe and select Run as administrator. Note: If you are prompted for an administrator password or confirmation, type your password, or click Continue. b. In the popup window, type the following commands and press Enter one by one: ipconfig /release ipconfig /renew Then, the new IP address will be obtained. If the issue persists, please proceed to the next steps. 4. Configure the connection to obtain an IP address automatically: a) Click "Start", input "NCPA.CPL" (without quotation marks) to Start Search bar and press "Enter". b) Right-click the network connection and click "Properties". If you are prompted for an administrator password or confirmation, type the password or provide confirmation. c) Click to highlight "Internet Protocol Version 6 (TCP/IPv6)" and click "Properties". d) Check "Obtain an IP address automatically" and "Obtain DNS server address automatically". e) Click "OK". f) Click to highlight "Internet Protocol Version 4 (TCP/IPv4)" and click "Properties". g) Check "Obtain an IP address automatically" and "Obtain DNS server address automatically". h) Click "OK". i) Reboot the computer. For more information, please also refer to the following articles: The network connectivity status incorrectly appears as "Local only" on a Windows Server 2008-based or Windows Vista-based computer that has more than one network adapter Appendix H: Network Connectivity Status Indicator and Resulting Internet Communication in Windows 7 and Windows Server 2008 R2 Regards, Sabrina TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please 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.

THIS IS THE FIX. NETWORK DISCOVERY MUST BE TURNED ON UNDER NETWORK; ADVANCED SETTINGS. OTHERWISE THE PC WILL NOT CONSISTENTLY CONNECT TO INTERNET PAGES AND DISPLAY "DIAGNOSE CONNECTION". THIS OPENS UP NEEDED COMMUNICATION THRU THE FIREWALL FOR THE PC TO WORK PROPERLY IN A WINDOWS 2003 DOMAIN ENVIRONMENT

That is not actually correct. Network Discovery is not required access to internet based web pages. Visit: anITKB.com, an IT Knowledge Base.

yep...it is still acting up.

I noticed one odd item....it hung on a web site....so I did a tracert to that site. It stalled at some internal address ebr-2300 192.168.2.189. it hung there. I pinged 192.168.2.189 and got no response. So I looked on the DHCP and DNS server and removed the entries for the 2.189 item. The user login seems to connect now much more consistently after I added Network Deiscovery. but I can't tell you what is wrong exactly. Unfortunately, Windows 7 has not been proven as reliable as Windows XP right now. Since 7 has been out a year, one would think this would be more easily fixable. I'm really concerned about unleasing this on users in our network....

Hi, Thank you for your feedback. And I am glad to hear that the issue was resolved. Please be assured that any improvements in the product are based on users' requirements. Our developers strive to capture Microsoft users' ideas and are working hard to create a more powerful and easy-to-use product. Regards, Sabrina TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please 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.

ACTUALLY, STILL HAVING THIS PROBLEM. NEVER REALLY RESOLVED IT. I HAVE 5 MORE PC'S WITH WINDOWS 7 SO MAYBE THAT WILL GIVE ME MORE TO GO ON.

Hi, First, I would like to confirm the result after taking my previous suggestions on the other computers. If there is any error encountered, please let me know the detailed symptom. Regards, Sabrina TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please 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.

New Dell Latitude E6510 and Optilex 780....both brand new running Windows 7 Professional and on a Windows 2003 domain network / Dell PowerConnect 1 gig switches.....Also have 80 pc's running Windows XP with no issues whatsoever. This is stricly a Windows 7 pc issue. I did everything you suggested....no error messages on renewing the NIC addresses, etc. Still takes up to 50 minutes before an successful internet connection comes up....I just get DIAGNOSE CONNECTION PROBLEMS.....

I will once again recommend as I did previously in this thread that you need to scope this issue properly. Is this a network or application layer issue. The only way to find out is to first run diagnostics at the network layer. I provided some insight on basic tools used to check for connectivity and name resolution. If you validate that this is or is not a network issue, you'll probably get some additional comments and suggestions. Visit: anITKB.com, an IT Knowledge Base.

Hi, As this thread has been quiet for a while, I was wondering how everything is going. If anything is unclear, please let me know. It is my pleasure to be of assistance. Regards, Sabrina TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comThis posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please 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.

still same problem...

I can ping the Domain Controllers....I get an IP address on the machines with no problem. DHCP does not show any errors. NSLOOKUP returns an answer...as below. When I try to ping www.yahoo.com. I get no answer. Tracert goes to the router on our gateway and times out. nslookup www.yahoo.com Server: King1.mtc.mansion.rosewoodhotels.local Address: 192.168.2.7 Non-authoritative answer: Name: any-fp.wal.b.yahoo.com Address: 209.191.122.70 Aliases: www.yahoo.com fp.wg1.b.yahoo.com

Carnold1, I have to agree with the troubleshooting steps and suggestions that were already offered, escpecially checking the log on the firewall to see if traffic from the systems experiencing the issue is making it to the firewall. Unfortunately using ping to test connectivity to Internet sites is generally not a usefull test as most sites are configured not to respond to ping for security reasons. If you are still seeing the issue I would suggest opening a paid support case with Microsoft Support. This will allow for a much deeper level of data analysis and troubleshooting. Please visit the below link to see the various paid support options that are available to better meet your needs. http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone Please 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. Regards, Clark Satter Microsoft Online Community Support

finally called Microsoft Support.....tech opened a command prompt and checked arp -a. Found that the MAC of the Gateway Router was not correct, it was picking up another MAC. I searched thru the MAC addresses on the switch and found that 2 Dell Powerconnect Managed Switches out of 7 on our network had the same address as the Gateway.....Apparently the Default IP on these Switches happens to be the same as our Internet Gateway. I reconfigured the Switches with a new unique IP address and now Windows 7 has no problems accessing the Internet. For some reason, the Windows XP machines on the network worked fine even with this network misconfiguration. Windows 7 apparently operates differently. Problem solved....somewhat painfully after 2 months.

Hi I have deployed a few windows 7 pro machines, also Dell Optiplex that are experiencing the exact same symptoms. i have done everyone of the highlighted steps above and am still having the issue. Did you ever fully resolve this issue? How?