Internet access but no network access

July 13, 2012 at 08:27:54
Specs: Windows Server 2008 R2
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>


See More: Internet access but no network access

Report •

#1
July 13, 2012 at 11:02:46
Sorry but you did not follow the proper procedure.

You do the rename and ip address AFTER you finished replicating with the old server and you dcpromo down the old server and remove its dns entry.

You need to get into the MS DNS server and update the host and ptr records for the servers so they are at the correct ip addresses and names. this will take care of the first and perhaps the 2nd errors in dcdiag.

these are redundent entries. choose one. more is not better.
192.168.0.3
127.0.0.1

It is also recommended you have two DCs for AD failover. Might want to not remove the old dc.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
July 13, 2012 at 11:41:27
I was pretty sure I did follow all the correct procedures and I did not make any name of IP address changes until after the replication was complete. That is why I am confused as to what happened. I will follow you suggestion and let you know what happens.

Also, if I am going to have two DCs how do I set up one to be the main DC? We have always, until now, had but one server though I know it is best prictice to have a backup. It is only due to the generosity of a school benefactor that we were able to purchase the second server.


Report •

#3
July 13, 2012 at 14:09:30
Active Directory is peer to peer so any server is the "main server". The way Microsoft determines which server to use is the one with the least load.

Having two ad servers does this:

duplicate DNS so both servers can be queried for name resolution
AD failover
Both should be global catalog holders

This does not mean the old dc is a "backup server" That is a completely different concept different from Active directory. Your "main server" is the one that holds the shares and user folders.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Related Solutions

#4
July 14, 2012 at 09:37:23
When I went into the server to update the host record I received an error message "the host record server2008.huntingtoncatholic.local could not be created. the record already exists." I did remove one of the IP addresses as instructed - 127.0.0.1 since the server has a static IP of 192.168.0.3.

Report •

#5
July 21, 2012 at 08:05:47
I only want to use one DC. So, what went wrong that the new DC is not the DC? I want it to be the DC since we have upgraded to Server 2008 and the age of the old server makes using it strictly as a backup the more prudent choice. Do I need to completely disconnect the network cable from the old DC? Do I need to run dcpromo again on the new server? No matter what I do I cannot demote the old server. I have some screen shots I could send that may give more information. Is there a way to attach files on this site?

Here is the latest dcdiag -

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>


Report •

Ask Question