Can't Connect to DC After R2 Upgrade

Hi,

We have a fairly major problem after performing the Win2003 R2 upgrade (From
Win2003 SP1). After performing the initial upgrade over Christmas I noticed
that for some reason after rebooting, I couldn't ping or connect to the DC
from other computers, I finally managed to solve this by disabling then
re-enabling the NIC, after which I could connect no problem.
However, that was last Thursday, and no one else was in the office. Now
everyone has come back from the holidays, and tried to connect, and it seems
that it has gone down again. Again I've had to disable/re-enable the NIC,
and it starts everything moving again, however, I don't know how long this
will stay up, it could go down again later this week, or later today.

Has anyone else had network issues after performing the upgrade? We're
running a Dell PowerEdge 2800, with Intel Pro 1000 MT Integrated Dual NIC.
I'm just going to check for the latest drivers, but thought I would ask if
anyone else has had a problem, or a possible solution while I do so!

Many thanks

Ben

Have also just noticed after performing the windows update and rebooting,
that the 'Initialising network connection' at start up has increased from a
couple of minutes (max 2), to about 10 minutes, and after logging on, the
NIC has problems again, and you have to disable/re-enable it, before you can
ping it/connect to the server via SMB.

Have upgraded the Intel Pro 1000 drivers to the latest (26th Nov 06), but it
hasn't helped.

Ben

Hi,
I had a similar problem but that was after i installed Microsoft patches. I
installed one by one in 10 of my servers but didnt face any problem, only one
server that is running storage edition of 2003 started giving problem where i
couldnt ping or access it.

But when i booted the server in Safe mode with networking I found it working
normally i.e. I could ping and access the shares. Then in suspected it is the
problem with some virus/spyware. So scanned every bit of it and found nothing.

finally i did the following:

netsh ip reset & netsh winsock reset.

Then I rebooted and it was good. But the only problem now is I cannot
connect to this server via remote desktop or symantec pcanywhere.

I tested all routes,dns settings everything all are proper. But this server
can no longer ping any m/c in the network with netbios or dns name but others
can ping and access it, dont know whats the problem.

--
Innu


"Ben" wrote:

> Hi,
>
> We have a fairly major problem after performing the Win2003 R2 upgrade (From
> Win2003 SP1). After performing the initial upgrade over Christmas I noticed
> that for some reason after rebooting, I couldn't ping or connect to the DC
> from other computers, I finally managed to solve this by disabling then
> re-enabling the NIC, after which I could connect no problem.
> However, that was last Thursday, and no one else was in the office. Now
> everyone has come back from the holidays, and tried to connect, and it seems
> that it has gone down again. Again I've had to disable/re-enable the NIC,
> and it starts everything moving again, however, I don't know how long this
> will stay up, it could go down again later this week, or later today.
>
> Has anyone else had network issues after performing the upgrade? We're
> running a Dell PowerEdge 2800, with Intel Pro 1000 MT Integrated Dual NIC.
> I'm just going to check for the latest drivers, but thought I would ask if
> anyone else has had a problem, or a possible solution while I do so!
>
> Many thanks
>
> Ben
>
>
>

Hi Innu,

Thanks for that, I will try both a "netsh ip reset" & a "netsh winsock
reset" tomorrow, and see if it solves the problem, I will report back!

Ben

"Oe" <(E-Mail Removed)> wrote in message
news:4A212560-6473-4505-A163-(E-Mail Removed)...
> Hi,
> I had a similar problem but that was after i installed Microsoft patches.
> I
> installed one by one in 10 of my servers but didnt face any problem, only
> one
> server that is running storage edition of 2003 started giving problem
> where i
> couldnt ping or access it.
>
> But when i booted the server in Safe mode with networking I found it
> working
> normally i.e. I could ping and access the shares. Then in suspected it is
> the
> problem with some virus/spyware. So scanned every bit of it and found
> nothing.
>
> finally i did the following:
>
> netsh ip reset & netsh winsock reset.
>
> Then I rebooted and it was good. But the only problem now is I cannot
> connect to this server via remote desktop or symantec pcanywhere.
>
> I tested all routes,dns settings everything all are proper. But this
> server
> can no longer ping any m/c in the network with netbios or dns name but
> others
> can ping and access it, dont know whats the problem.
>
> --
> Innu
>
>
> "Ben" wrote:
>
>> Hi,
>>
>> We have a fairly major problem after performing the Win2003 R2 upgrade
>> (From
>> Win2003 SP1). After performing the initial upgrade over Christmas I
>> noticed
>> that for some reason after rebooting, I couldn't ping or connect to the
>> DC
>> from other computers, I finally managed to solve this by disabling then
>> re-enabling the NIC, after which I could connect no problem.
>> However, that was last Thursday, and no one else was in the office. Now
>> everyone has come back from the holidays, and tried to connect, and it
>> seems
>> that it has gone down again. Again I've had to disable/re-enable the NIC,
>> and it starts everything moving again, however, I don't know how long
>> this
>> will stay up, it could go down again later this week, or later today.
>>
>> Has anyone else had network issues after performing the upgrade? We're
>> running a Dell PowerEdge 2800, with Intel Pro 1000 MT Integrated Dual
>> NIC.
>> I'm just going to check for the latest drivers, but thought I would ask
>> if
>> anyone else has had a problem, or a possible solution while I do so!
>>
>> Many thanks
>>
>> Ben
>>
>>
>>

Hmmm,

Well I decided to connect via VPN (no one in the office, so server rebooting
is less disrupted) and try out the 'netsh int ip reset' on the DC, then
rebooted the server...and now I can't connect to it again, seems the NIC is
still playing up :-( I'll have to disable/re-enable the NIC again in the
morning!

Does anyone else have any ideas on what's causing this issue?

Ben


"Ben" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Innu,
>
> Thanks for that, I will try both a "netsh ip reset" & a "netsh winsock
> reset" tomorrow, and see if it solves the problem, I will report back!
>
> Ben
>
> "Oe" <(E-Mail Removed)> wrote in message
> news:4A212560-6473-4505-A163-(E-Mail Removed)...
>> Hi,
>> I had a similar problem but that was after i installed Microsoft patches.
>> I
>> installed one by one in 10 of my servers but didnt face any problem, only
>> one
>> server that is running storage edition of 2003 started giving problem
>> where i
>> couldnt ping or access it.
>>
>> But when i booted the server in Safe mode with networking I found it
>> working
>> normally i.e. I could ping and access the shares. Then in suspected it is
>> the
>> problem with some virus/spyware. So scanned every bit of it and found
>> nothing.
>>
>> finally i did the following:
>>
>> netsh ip reset & netsh winsock reset.
>>
>> Then I rebooted and it was good. But the only problem now is I cannot
>> connect to this server via remote desktop or symantec pcanywhere.
>>
>> I tested all routes,dns settings everything all are proper. But this
>> server
>> can no longer ping any m/c in the network with netbios or dns name but
>> others
>> can ping and access it, dont know whats the problem.
>>
>> --
>> Innu
>>
>>
>> "Ben" wrote:
>>
>>> Hi,
>>>
>>> We have a fairly major problem after performing the Win2003 R2 upgrade
>>> (From
>>> Win2003 SP1). After performing the initial upgrade over Christmas I
>>> noticed
>>> that for some reason after rebooting, I couldn't ping or connect to the
>>> DC
>>> from other computers, I finally managed to solve this by disabling then
>>> re-enabling the NIC, after which I could connect no problem.
>>> However, that was last Thursday, and no one else was in the office. Now
>>> everyone has come back from the holidays, and tried to connect, and it
>>> seems
>>> that it has gone down again. Again I've had to disable/re-enable the
>>> NIC,
>>> and it starts everything moving again, however, I don't know how long
>>> this
>>> will stay up, it could go down again later this week, or later today.
>>>
>>> Has anyone else had network issues after performing the upgrade? We're
>>> running a Dell PowerEdge 2800, with Intel Pro 1000 MT Integrated Dual
>>> NIC.
>>> I'm just going to check for the latest drivers, but thought I would ask
>>> if
>>> anyone else has had a problem, or a possible solution while I do so!
>>>
>>> Many thanks
>>>
>>> Ben
>>>
>>>
>>>
>
>

In news:%2307%(E-Mail Removed),
Ben <(E-Mail Removed)> stated, which I commented on below:
> Hi,
>
> We have a fairly major problem after performing the Win2003 R2
> upgrade (From Win2003 SP1). After performing the initial upgrade over
> Christmas I noticed that for some reason after rebooting, I couldn't
> ping or connect to the DC from other computers, I finally managed to
> solve this by disabling then re-enabling the NIC, after which I could
> connect no problem. However, that was last Thursday, and no one else was
> in the office.
> Now everyone has come back from the holidays, and tried to connect,
> and it seems that it has gone down again. Again I've had to
> disable/re-enable the NIC, and it starts everything moving again,
> however, I don't know how long this will stay up, it could go down
> again later this week, or later today.
> Has anyone else had network issues after performing the upgrade? We're
> running a Dell PowerEdge 2800, with Intel Pro 1000 MT Integrated Dual
> NIC. I'm just going to check for the latest drivers, but thought I
> would ask if anyone else has had a problem, or a possible solution
> while I do so!
> Many thanks
>
> Ben

This sounds like a classic DNS problem and/or misconfigured domain name, but
have NO idea at this point because you DID NOT post any condiguration info.
Just by the fact that you mentioned in your other post it take now multiple
minutes instead of about two minutes to logon, tells me there may be a DNS
issue PRIOR to your R2 upgrade. Logons, or " 'Initializing network
connection" should NOT take two minutes, but rather only 10-20 seconds MAX.

Here are some possible causes:
1. Single label name.
2. SRV records missing.
3. Disjointed namespace.- AD domain name doesn't match the Primary DNS
Suffix and/or the zone name.
4. Using an ISP's DNS in IP properties of the DC and clients.
5. DHCP Client service disabled.
6. DC is multihomed
7. 3rd party firewalls
8. etc....


If you like to get specific help to diagnose this issue, and to elimiante
guesswork on our part, for starters, please post the following information:
1. Unedited ipconfig /all from two of your DCs, and one of your clients..
2. The exact zone name spellng in DNS and whether updates are allowed on the
zone.
3. The AD DNS domain name as it shows up in ADUC.
4. If the SRV records exist under your zone.
5. Any errors in the Event logs on the DC under System, Replication Service
and Directory Services (post the Event ID# and source please)
6. Dcdiag /v /fix > c:\dcdiag.txt (post the dcdiag.txt as an attachment)
7. Netdiag /v /fix > c:\netdiag.txt (post the dcdiag.txt as an attachment)
8. More than one subnet?
9. Forwarder(s) configured?


--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Infinite Diversities in Infinite Combinations
Assimilation Imminent. Resistance is Futile
"Very funny Scotty. Now, beam down my clothes."

The only constant in life is change...

Ah, after getting into the office, I found that the 'netsh int ip reset'
command had reset the servers IP address from static to DHCP, and the server
itself is our DHCP server, which is why I couldn't connect. After giving it
back its old static IP address, I tried a reboot again, and everything
seemed to be working properly again, start-up time is back down to 2
minutes, and other servers/clients can ping it with out having to
disable/re-enabling the NIC.

Seems to have been a corrupted TCP/IP stack!

Ben


"Ben" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hmmm,
>
> Well I decided to connect via VPN (no one in the office, so server
> rebooting is less disrupted) and try out the 'netsh int ip reset' on the
> DC, then rebooted the server...and now I can't connect to it again, seems
> the NIC is still playing up :-( I'll have to disable/re-enable the NIC
> again in the morning!
>
> Does anyone else have any ideas on what's causing this issue?
>
> Ben
>
>
> "Ben" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi Innu,
>>
>> Thanks for that, I will try both a "netsh ip reset" & a "netsh winsock
>> reset" tomorrow, and see if it solves the problem, I will report back!
>>
>> Ben
>>
>> "Oe" <(E-Mail Removed)> wrote in message
>> news:4A212560-6473-4505-A163-(E-Mail Removed)...
>>> Hi,
>>> I had a similar problem but that was after i installed Microsoft
>>> patches. I
>>> installed one by one in 10 of my servers but didnt face any problem,
>>> only one
>>> server that is running storage edition of 2003 started giving problem
>>> where i
>>> couldnt ping or access it.
>>>
>>> But when i booted the server in Safe mode with networking I found it
>>> working
>>> normally i.e. I could ping and access the shares. Then in suspected it
>>> is the
>>> problem with some virus/spyware. So scanned every bit of it and found
>>> nothing.
>>>
>>> finally i did the following:
>>>
>>> netsh ip reset & netsh winsock reset.
>>>
>>> Then I rebooted and it was good. But the only problem now is I cannot
>>> connect to this server via remote desktop or symantec pcanywhere.
>>>
>>> I tested all routes,dns settings everything all are proper. But this
>>> server
>>> can no longer ping any m/c in the network with netbios or dns name but
>>> others
>>> can ping and access it, dont know whats the problem.
>>>
>>> --
>>> Innu
>>>
>>>
>>> "Ben" wrote:
>>>
>>>> Hi,
>>>>
>>>> We have a fairly major problem after performing the Win2003 R2 upgrade
>>>> (From
>>>> Win2003 SP1). After performing the initial upgrade over Christmas I
>>>> noticed
>>>> that for some reason after rebooting, I couldn't ping or connect to the
>>>> DC
>>>> from other computers, I finally managed to solve this by disabling then
>>>> re-enabling the NIC, after which I could connect no problem.
>>>> However, that was last Thursday, and no one else was in the office. Now
>>>> everyone has come back from the holidays, and tried to connect, and it
>>>> seems
>>>> that it has gone down again. Again I've had to disable/re-enable the
>>>> NIC,
>>>> and it starts everything moving again, however, I don't know how long
>>>> this
>>>> will stay up, it could go down again later this week, or later today.
>>>>
>>>> Has anyone else had network issues after performing the upgrade? We're
>>>> running a Dell PowerEdge 2800, with Intel Pro 1000 MT Integrated Dual
>>>> NIC.
>>>> I'm just going to check for the latest drivers, but thought I would ask
>>>> if
>>>> anyone else has had a problem, or a possible solution while I do so!
>>>>
>>>> Many thanks
>>>>
>>>> Ben
>>>>
>>>>
>>>>
>>
>>
>
>

"Ace Fekay [MVP]" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...

<snip>
>
> This sounds like a classic DNS problem and/or misconfigured domain name,
> but have NO idea at this point because you DID NOT post any condiguration
> info. Just by the fact that you mentioned in your other post it take now
> multiple minutes instead of about two minutes to logon, tells me there may
> be a DNS issue PRIOR to your R2 upgrade. Logons, or " 'Initializing
> network connection" should NOT take two minutes, but rather only 10-20
> seconds MAX.
>
> Here are some possible causes:
> 1. Single label name.
> 2. SRV records missing.
> 3. Disjointed namespace.- AD domain name doesn't match the Primary DNS
> Suffix and/or the zone name.
> 4. Using an ISP's DNS in IP properties of the DC and clients.
> 5. DHCP Client service disabled.
> 6. DC is multihomed
> 7. 3rd party firewalls
> 8. etc....
>
>
> If you like to get specific help to diagnose this issue, and to elimiante
> guesswork on our part, for starters, please post the following
> information:
> 1. Unedited ipconfig /all from two of your DCs, and one of your clients..
> 2. The exact zone name spellng in DNS and whether updates are allowed on
> the zone.
> 3. The AD DNS domain name as it shows up in ADUC.
> 4. If the SRV records exist under your zone.
> 5. Any errors in the Event logs on the DC under System, Replication
> Service and Directory Services (post the Event ID# and source please)
> 6. Dcdiag /v /fix > c:\dcdiag.txt (post the dcdiag.txt as an attachment)
> 7. Netdiag /v /fix > c:\netdiag.txt (post the dcdiag.txt as an attachment)
> 8. More than one subnet?
> 9. Forwarder(s) configured?
>
>
> --
> Ace
> Innovative IT Concepts, Inc (IITCI)
> Willow Grove, PA
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Directory Services
> Microsoft Certified Trainer

Hi Ace,

Thanks for the reply.

I'm not keen on posting too much information on our setup, as I know hackers
and such search NGs for any information that might help them.

I don't think this was a DNS problem, after performing a 'netsh int ip
reset' and rebooting, everything seems to be back up and running with out
problem.

The start-up time is back to about 2 minutes, this includes everything from
initialising windows, network connections, and applying all policies. As you
said, the actual time to initialise network connections is now about 20
seconds, rather than the previous 10 mins.

I think this must be due to a corrupt TCP/IP stack, or something caused by
the R2 upgrade.

Many thanks

Ben

In news:(E-Mail Removed),
Ben <(E-Mail Removed)> stated, which I commented on below:
> Hi Ace,
>
> Thanks for the reply.
>
> I'm not keen on posting too much information on our setup, as I know
> hackers and such search NGs for any information that might help them.
>
> I don't think this was a DNS problem, after performing a 'netsh int ip
> reset' and rebooting, everything seems to be back up and running with
> out problem.
>
> The start-up time is back to about 2 minutes, this includes
> everything from initialising windows, network connections, and
> applying all policies. As you said, the actual time to initialise
> network connections is now about 20 seconds, rather than the previous
> 10 mins.
> I think this must be due to a corrupt TCP/IP stack, or something
> caused by the R2 upgrade.
>
> Many thanks
>
> Ben

If you are behind a firewall and have a private domain name with private IP
addresses, then I really don't see the problem. Many installations have IP
addresses such as 192.168.1.x, or 10.x.x.x., etc. But that is your call and
understand trying to be security conscience. You also have the option to
keep it private by emailing it to someone trying to assist you as well.

But keep in mind, it;s like going to the doc and telling him/her it hurts.
What hurts? Where? Symptoms? Etc...

As doctors do, we are here trying to help out anyone and everyone that needs
help. But we need help as well to help you.

But I see you figured out what's wrong and fixed it. Good to hear...

Ace