microsoft.public.windows.server.networking

Hello Everyone.

I seem to have developed a problem after installing SP1. I have two of
these boxes doing the exact same thing. Luckily I'm still in the
pre-production environment.

Before installing Sp1 I have adapter 1 with ip address 90.0.0.153 and
adapter 2 with 90.0.0.53. I reboot the server wait 10 minutes and then
Ping both interfaces from my desktop 0% packet loss on adapter 1 and 2.
I then install sp1. I reboot as requested. I then wait 5 minutes and
ping both adapters again. Adapter #1 fires back with 0% packet loss. I
then ping adapter 2 and end up with 25% packet loss. It appears the
First ping (out of 4) never made it to the destination. So I wait 5
minutes and try again.. Only to be greeted with the same problem. So I
rebooted thinking that may clear the air. And I'm still with the same
problem with the first packet seeming disappearing.

I have been Looking around the Forums / Usenet / etc.. Looking for
possibilities and have come up empty handed. Since this did happen
after installing Sp1 I'm convinced that Sp1 is to blame. Also uninstall
sp1 doesn't fix this issue. ( I've reinstall from scratch 3 times just
to make sure I wasn't screwing something up. Before I did reinstall I
was installing software into this server (it's running terminal
services as well) at one point I was using rdp to get into the machine
yet couldn't connect to a mapped drive, couldn't browse the local
network (via My Computer address bar \\name\share or \\ip\share. A
reboot did make that condition go away but I can't help but think they
are related somehow.

Any Ideas would be greatly appreciated.

I am surprised that it worked before. What is the purpose of two NICs in
the same IP subnet? What are they supposed to do?

Packetscan wrote:
> Hello Everyone.
>
> I seem to have developed a problem after installing SP1. I have two of
> these boxes doing the exact same thing. Luckily I'm still in the
> pre-production environment.
>
> Before installing Sp1 I have adapter 1 with ip address 90.0.0.153 and
> adapter 2 with 90.0.0.53. I reboot the server wait 10 minutes and then
> Ping both interfaces from my desktop 0% packet loss on adapter 1 and
> 2. I then install sp1. I reboot as requested. I then wait 5 minutes
> and ping both adapters again. Adapter #1 fires back with 0% packet
> loss. I then ping adapter 2 and end up with 25% packet loss. It
> appears the First ping (out of 4) never made it to the destination.
> So I wait 5 minutes and try again.. Only to be greeted with the same
> problem. So I rebooted thinking that may clear the air. And I'm
> still with the same problem with the first packet seeming
> disappearing.
>
> I have been Looking around the Forums / Usenet / etc.. Looking for
> possibilities and have come up empty handed. Since this did happen
> after installing Sp1 I'm convinced that Sp1 is to blame. Also
> uninstall sp1 doesn't fix this issue. ( I've reinstall from scratch 3
> times just to make sure I wasn't screwing something up. Before I did
> reinstall I was installing software into this server (it's running
> terminal services as well) at one point I was using rdp to get into
> the machine yet couldn't connect to a mapped drive, couldn't browse
> the local network (via My Computer address bar \\name\share or
> \\ip\share. A reboot did make that condition go away but I can't help
> but think they are related somehow.
>
> Any Ideas would be greatly appreciated.

The Purpose of two nics is to provide some fail over and increase
throughput.

First there are two switches that then feed into the back bone.
One adapter to one switch and the other adapter goes into the other
switch.

This is how i have my 2000 servers setup and it works flawlessly.

Thanks in advance

Well to add to this mystery i've gone into the bios and disabled one of
the nic cards.
I am still experiencing this problem. Even with one adapter.
So the next step was to enable the currently disabled nic and disable
the nic that was enabled. The problem followed to the other nic.
So i'm back with two adapters one works flawles the other drops the
first packet sent from any machine , Ping, Dns request, etc..

The only way that works properly is by using NIC teaming. Just putting
two NICs in the same IP subnet doesn't do it for you.

The extra security features in SP1 almost certainly have caused this to
happen now. But it is not a good idea and shouldn't have worked before. How
do you use the second NIC apart from pinging it by its IP address? What IP
does the name of the machine resolve to? Which NIC is at the top of the
binding order?

Packetscan wrote:
> The Purpose of two nics is to provide some fail over and increase
> throughput.
>
> First there are two switches that then feed into the back bone.
> One adapter to one switch and the other adapter goes into the other
> switch.
>
> This is how i have my 2000 servers setup and it works flawlessly.
>
> Thanks in advance

ok say server has 90.0.0.52 assigned to adapter #1 and 90.0.0.152
assigned to adapter #2. If i switch and have 52 on #2 and 152 on #1.
This ping issue will follow the lower value Ip. (52 in this case).

Why i use both nic's: Everything in DNS is roundrobin so i figured it
would never load up just one of the nic's. What security features could
be causeing this? I don't have the firewall enabled.

Also i've gone as far as to disable one of the nics in the bios of the
motherboard as they are intergrated. When i only have one network card
seen by windows i still have this ping problem. and it only develops
after installing sp1. and uninstall sp1 doesn't undo the changes and
i'm left with this issue.

On a side note i have two domain controllers with sp1 installed and
using both nics without teaming or network loadblaancing and i don't
have this issue the only difference is that those machines are single
proc and these machine with the ping problem are dualies


Bill Grant wrote:
> The only way that works properly is by using NIC teaming. Just putting
> two NICs in the same IP subnet doesn't do it for you.
>
> The extra security features in SP1 almost certainly have caused this to
> happen now. But it is not a good idea and shouldn't have worked before. How
> do you use the second NIC apart from pinging it by its IP address? What IP
> does the name of the machine resolve to? Which NIC is at the top of the
> binding order?
>