Up untilrecently I've been running Server Standard RC0 and everything was working perfectly. Since the RC0 license expired, the computer began restarting roughly every few hours and wouldn't connect to the internet (though the website it was hosting could still be accessed). I assumed these issues were because of the expired RC0 license key so Iupgraded to Server Enterprise using the 60 day extendable trial (trying to hold off until MSDNAA product keys become available). The computer doesn't restart now, but I still can't get online due to the netowork issue. When I hover over the network icon in the task bar, it reads the same thing it said just before I upgraded from RC0: "Currently connected to: Network Access: Local only" I doubt the issue is with the router. I have other computers hooked up to it both wired and wirelessly and the router is still forwarding incoming requests to the router just like it should (the webpage is still up and running even withthe network issue). I would really like to avoid a clean install so any help would be much appreciated. Thank you!

Can you hook a PC up to this machine with a cross-over cable? I think that will give you an air-tight testing scenario. You can connect by IP addresses and the like to see if you can access resources external to the server and from an external source. If this doesnt work, can you post an IP config? Look at your gateway, and make sure that it is set to your router. Let me know what you find,

Sorry, been a bit busy lately. Here's the ipconfig. ********************************************************** Microsoft Windows [Version 6.0.6001]Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\******>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Entertain-Serv Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 00-E0-4D-09-16-BA DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::118e:2cca:19b5:6a5%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.123(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 74.134.1.180 47.134.1.181 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection*: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\Administrator>nfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Entertain-Serv Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 00-E0-4D-09-16-BA DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::118e:2cca:19b5:6a5%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.123(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 74.134.1.180 47.134.1.181 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Local Area Connection*: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes ********************************************************************************* I'm not sure what you meant for me to do with the crossover calbe, but the server is currently hosting a webpage and an ftp server that'saccessable from the internet...... so basically the internet can see and access the server, but the server refuses toacknowlege that internet is there.

Can you ping 192.168.1.1? If you can, can you try to manage the router that is at that IP address? Also, go to the command line and "tracert www.google.com" and let me know what you see.

Hello, Please check whether other machines in the same LAN behind the router could access the internet. If not, please check whether there are any blocking outgoing traffic policies set on the router. If other machines in the same LAN could access the internet, please try the following steps to narrow down the issue: 1. Please temporarily disable Windows firewall and check whether this will make any difference. 2. Please try to disable IPv6 in Windows Server 2008 by doing one of the following steps and have another try: In the Network Connections folder, obtain properties on all of your connections and adapters and clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under This connection uses the following items. Add the following registry value (DWORD type) set to 0xFF: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents This method disables IPv6 on all your LAN interfaces, connections, and tunnel interfaces but does not disable the IPv6 loopback interface. You must restart the computer for this registry value to take effect. Please let me know the result after you finish the tests. Thanks. Regards, Neo Zhu

Thanks a lot Jian, as I was checking the IPv6 I checked the other internet seetings against my router's and for some reason the static IP the router was using before was now being rejected by the router. I think the problem stemmed from my ISP.A reset on their end and re-working the static IPv4 settings fixed the "local only" problem.

Hello, Thank you for your update. I'm glad to hear this issue has been solved. -Neo Zhu