Server 2008 - Internet Access but no Network access

[mrtechno77]

I am upgrading our servers from Windows Server 2003 to 2008 R2. I thought I had followed the Microsoft instructions to achieve this but must have missed something somewhere.

I set the new server's IP addrsss to that of the old DC and am on the appropriate network with the server. I also changed the IP address on the old DC so as not to conflict on the network. I renamed the old DC but was unable to rename the new DC to the original name of the old one. I also was unable to demote the old PC or remove it from the domain.

I checked the bindings and the DNS settings.. I am posting the results from ipconfig /all and dcdiag. In dcdiag it says to check firewall settings. If I click to use recommended settings" I get the message that the firewall is managed by Group Policy settings and that only an administrator can change it. I am logged in as administrator so I don't understand why I can make changes if I need to. Please respond. Our client systems have access to the Internet but not the network. If I try to log on as a known user on a client I get the message that I am being logged on with a temporary profile. Also, even logged on as administrator I can't map any network drives and can not even see the network when I try. Please advise.

Thank you!

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator.CATHOLIC>dcdiag

Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = Server2008
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\SERVER2008
Starting test: Connectivity
The host
65e60394-6e60-4229-9fe1-3fce23252942._msdcs.HuntingtonCatholic.local
could not be resolved to an IP address. Check the DNS server, DHCP,
server name, etc.
Got error while checking LDAP and RPC connectivity. Please check your
firewall settings.
......................... SERVER2008 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site\SERVER2008
Skipping all tests, because server SERVER2008 is not responding to
directory service requests.


Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation

Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation

Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation

Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation

Running partition tests on : HuntingtonCatholic
Starting test: CheckSDRefDom
......................... HuntingtonCatholic passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... HuntingtonCatholic passed test
CrossRefValidation

Running enterprise tests on : HuntingtonCatholic.local
Starting test: LocatorCheck
......................... HuntingtonCatholic.local passed test
LocatorCheck
Starting test: Intersite
......................... HuntingtonCatholic.local passed test
Intersite

C:\Users\Administrator.CATHOLIC>


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator.CATHOLIC>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Server2008
Primary Dns Suffix . . . . . . . : HuntingtonCatholic.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : HuntingtonCatholic.local

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
Physical Address. . . . . . . . . : 00-0F-20-F8-FD-68
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-0F-20-F8-FD-69
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8415:7d0:be82:e9f2%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.250
DHCPv6 IAID . . . . . . . . . . . : 234884896
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-17-5B-E4-24-00-0F-20-F8-FD-69

DNS Servers . . . . . . . . . . . : ::1
192.168.0.3
127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{AE356FD3-4709-4699-9F09-E5EA7120CCA3}:

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

Tunnel adapter isatap.{0D27CDD0-7404-44C4-B821-8046EA2B4A81}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
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\Administrator.CATHOLIC>

 

[ShackDaddy]

This AD is hosed up in several directions. You can't handle name and IP changes the way you did without creating problems.

The first place I would go would be to open the DNS management console on each DC and change any faulty records. I would delete the long GUID records in the MSDCS root domain, as they are easy to recreate and the DCDIAG indicates they are currently pointed to bad IPs. I would also do "IPCONFIG /REGISTERDNS" on both DC's and restart the NETLOGON service on both DCs and see what the DNS records looked like after that, since that should create the proper ones. If they don't have screwed up trust or bad Kerberos tickets, this may be enough to fix things.

Dave Shackelford
ThirdTier.net
TrainSignal.com