Need Help from Advanced IP Routing Tech

Hello--

This one boggles the mind. We have gone to multiple experts and still there
are several websites that we host on a local IIS server that we cannot access
from workstations from within the same subnet.

We host our DNS and the addresses resolve nicely. Here's our setup--maybe
someone can help us figure this one out.

We host multiple websites on our W 2003 server via IIS v 6.0. For each web
address we have it's associated IP address manually entered into the server's
NIC card's advanced properties. The main IP address on the NIC card is
associated with a website that we have no problem accessing. Only the
"additional" IP address are giving us problems accessing.

As part of our troubleshooting, I entered into the NIC card one of the IP
addresses that we are having issues with as the primary IP address and that
solved the issue. Again, it is only the additional IP address on the NIC that
are causing problems.

I can ping our DC from the IIS server and I can ping the main IP address of
the IIS server from the DC, but when I ping one of the additional IP address
of the IIS server from the DC, the first packet is received, but the next 75%
are lost.

Now here is where I am ignorant: why am I getting a different physical
address for the additional IP addresses than the main IP address when I do an
arp -a test? That seems very strange to me. Should there only be one physical
address for one NIC card?

Any help would be greatly appreciated.

Razor,
If you can't ping the additional IP addresses of the server there is
something wrong with your setup. There is nothing in the description you
have given to indicate what it might be.
You would need to describe the network and the servers further to get a
resolution,
Anthony -
http://www.airdesk.co.uk



"razor" <(E-Mail Removed)> wrote in message
news:C972C022-AEFC-4FB6-91FE-(E-Mail Removed)...
> Hello--
>
> This one boggles the mind. We have gone to multiple experts and still
> there
> are several websites that we host on a local IIS server that we cannot
> access
> from workstations from within the same subnet.
>
> We host our DNS and the addresses resolve nicely. Here's our setup--maybe
> someone can help us figure this one out.
>
> We host multiple websites on our W 2003 server via IIS v 6.0. For each web
> address we have it's associated IP address manually entered into the
> server's
> NIC card's advanced properties. The main IP address on the NIC card is
> associated with a website that we have no problem accessing. Only the
> "additional" IP address are giving us problems accessing.
>
> As part of our troubleshooting, I entered into the NIC card one of the IP
> addresses that we are having issues with as the primary IP address and
> that
> solved the issue. Again, it is only the additional IP address on the NIC
> that
> are causing problems.
>
> I can ping our DC from the IIS server and I can ping the main IP address
> of
> the IIS server from the DC, but when I ping one of the additional IP
> address
> of the IIS server from the DC, the first packet is received, but the next
> 75%
> are lost.
>
> Now here is where I am ignorant: why am I getting a different physical
> address for the additional IP addresses than the main IP address when I do
> an
> arp -a test? That seems very strange to me. Should there only be one
> physical
> address for one NIC card?
>
> Any help would be greatly appreciated.

As I said, I can ping it with the first 25%. What additional information do
you need? I listed what I thought was pertinent to start a dialog with anyone
with experience in this area to try to help me troubleshoot. Define "setup"
DNS, AD, IIS, IP, etc.?? What are you asking??

Thanks,

sd

"Anthony" wrote:

> Razor,
> If you can't ping the additional IP addresses of the server there is
> something wrong with your setup. There is nothing in the description you
> have given to indicate what it might be.
> You would need to describe the network and the servers further to get a
> resolution,
> Anthony -
> http://www.airdesk.co.uk
>
>
>
> "razor" <(E-Mail Removed)> wrote in message
> news:C972C022-AEFC-4FB6-91FE-(E-Mail Removed)...
> > Hello--
> >
> > This one boggles the mind. We have gone to multiple experts and still
> > there
> > are several websites that we host on a local IIS server that we cannot
> > access
> > from workstations from within the same subnet.
> >
> > We host our DNS and the addresses resolve nicely. Here's our setup--maybe
> > someone can help us figure this one out.
> >
> > We host multiple websites on our W 2003 server via IIS v 6.0. For each web
> > address we have it's associated IP address manually entered into the
> > server's
> > NIC card's advanced properties. The main IP address on the NIC card is
> > associated with a website that we have no problem accessing. Only the
> > "additional" IP address are giving us problems accessing.
> >
> > As part of our troubleshooting, I entered into the NIC card one of the IP
> > addresses that we are having issues with as the primary IP address and
> > that
> > solved the issue. Again, it is only the additional IP address on the NIC
> > that
> > are causing problems.
> >
> > I can ping our DC from the IIS server and I can ping the main IP address
> > of
> > the IIS server from the DC, but when I ping one of the additional IP
> > address
> > of the IIS server from the DC, the first packet is received, but the next
> > 75%
> > are lost.
> >
> > Now here is where I am ignorant: why am I getting a different physical
> > address for the additional IP addresses than the main IP address when I do
> > an
> > arp -a test? That seems very strange to me. Should there only be one
> > physical
> > address for one NIC card?
> >
> > Any help would be greatly appreciated.
>
>
>

1. Disable (unbind, uncheck the box) NLB in the properties of the Nic and
any other Nic on the machine.

2. Make sure you don't have a duplicate IP problem on the LAN segment.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"razor" <(E-Mail Removed)> wrote in message
news:C972C022-AEFC-4FB6-91FE-(E-Mail Removed)...
> Hello--
>
> This one boggles the mind. We have gone to multiple experts and still
> there
> are several websites that we host on a local IIS server that we cannot
> access
> from workstations from within the same subnet.
>
> We host our DNS and the addresses resolve nicely. Here's our setup--maybe
> someone can help us figure this one out.
>
> We host multiple websites on our W 2003 server via IIS v 6.0. For each web
> address we have it's associated IP address manually entered into the
> server's
> NIC card's advanced properties. The main IP address on the NIC card is
> associated with a website that we have no problem accessing. Only the
> "additional" IP address are giving us problems accessing.
>
> As part of our troubleshooting, I entered into the NIC card one of the IP
> addresses that we are having issues with as the primary IP address and
> that
> solved the issue. Again, it is only the additional IP address on the NIC
> that
> are causing problems.
>
> I can ping our DC from the IIS server and I can ping the main IP address
> of
> the IIS server from the DC, but when I ping one of the additional IP
> address
> of the IIS server from the DC, the first packet is received, but the next
> 75%
> are lost.
>
> Now here is where I am ignorant: why am I getting a different physical
> address for the additional IP addresses than the main IP address when I do
> an
> arp -a test? That seems very strange to me. Should there only be one
> physical
> address for one NIC card?
>
> Any help would be greatly appreciated.

The NICs are not teamed--but I would like to know how to check for duplicate
IP addresses other than our DNS or DHCP records? Is there any way to see if
there is another device that has an IP address assigned to it?

Thanks,

sd

"Phillip Windell" wrote:

> 1. Disable (unbind, uncheck the box) NLB in the properties of the Nic and
> any other Nic on the machine.
>
> 2. Make sure you don't have a duplicate IP problem on the LAN segment.
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
> "razor" <(E-Mail Removed)> wrote in message
> news:C972C022-AEFC-4FB6-91FE-(E-Mail Removed)...
> > Hello--
> >
> > This one boggles the mind. We have gone to multiple experts and still
> > there
> > are several websites that we host on a local IIS server that we cannot
> > access
> > from workstations from within the same subnet.
> >
> > We host our DNS and the addresses resolve nicely. Here's our setup--maybe
> > someone can help us figure this one out.
> >
> > We host multiple websites on our W 2003 server via IIS v 6.0. For each web
> > address we have it's associated IP address manually entered into the
> > server's
> > NIC card's advanced properties. The main IP address on the NIC card is
> > associated with a website that we have no problem accessing. Only the
> > "additional" IP address are giving us problems accessing.
> >
> > As part of our troubleshooting, I entered into the NIC card one of the IP
> > addresses that we are having issues with as the primary IP address and
> > that
> > solved the issue. Again, it is only the additional IP address on the NIC
> > that
> > are causing problems.
> >
> > I can ping our DC from the IIS server and I can ping the main IP address
> > of
> > the IIS server from the DC, but when I ping one of the additional IP
> > address
> > of the IIS server from the DC, the first packet is received, but the next
> > 75%
> > are lost.
> >
> > Now here is where I am ignorant: why am I getting a different physical
> > address for the additional IP addresses than the main IP address when I do
> > an
> > arp -a test? That seems very strange to me. Should there only be one
> > physical
> > address for one NIC card?
> >
> > Any help would be greatly appreciated.
>
>
>

That is difficult to do. When it is "acting up" and you are seeing the
strange MAC address, you need to remove the IP# from the server and "stop"
the Site associated with it,...then with the server "out of the way" try to
ping the IP# and see if "something" responds,...if that MAC belongs to
something it should respond.

If something responds then I don't know of any easy way to locate it other
than physically examine each machine in that Segment one at a time. There
is nothing about Ethernet that will physically locate a machine, but you may
be able to examine the ARP Table in the switches and see if that rogue MAC
appears in the switches and at least narrow it down to what switch it is
connected to. However, keep in mind that it may be listed in all the
switches but will associate with a port that is connected to another switch
meaning that it is actually on another upstream switch. You keep following
it until to get to a switch that shows the MAC on a port that has a specific
IP Device (like a PC) plugged into it.

In fact you may be able to track that MAC if you know what it is even with
the Server online since you don't need any IP#s to do that. However the ARP
TTL in the ARP Tables is short.

Tools like NetScan from SoftPerfect may be somewhat helpful, but your
switches management interface (Telnet or HTTP) would be how to track the ARP
Tables.

I've had to follow this process when I had even legitament IP/Mac pairs that
I just simply didn't have a record of what device they belonged to. I used
the IP# to find the MAC and then tracked the MAC through the Switches till I
got to the specific Port on the specific Switch.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"razor" <(E-Mail Removed)> wrote in message
news:5248B476-DF73-4F82-92A3-(E-Mail Removed)...
> The NICs are not teamed--but I would like to know how to check for
> duplicate
> IP addresses other than our DNS or DHCP records? Is there any way to see
> if
> there is another device that has an IP address assigned to it?
>
> Thanks,
>
> sd
>
> "Phillip Windell" wrote:
>
>> 1. Disable (unbind, uncheck the box) NLB in the properties of the Nic and
>> any other Nic on the machine.
>>
>> 2. Make sure you don't have a duplicate IP problem on the LAN segment.
>>
>> --
>> Phillip Windell
>> www.wandtv.com
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>> "razor" <(E-Mail Removed)> wrote in message
>> news:C972C022-AEFC-4FB6-91FE-(E-Mail Removed)...
>> > Hello--
>> >
>> > This one boggles the mind. We have gone to multiple experts and still
>> > there
>> > are several websites that we host on a local IIS server that we cannot
>> > access
>> > from workstations from within the same subnet.
>> >
>> > We host our DNS and the addresses resolve nicely. Here's our
>> > setup--maybe
>> > someone can help us figure this one out.
>> >
>> > We host multiple websites on our W 2003 server via IIS v 6.0. For each
>> > web
>> > address we have it's associated IP address manually entered into the
>> > server's
>> > NIC card's advanced properties. The main IP address on the NIC card is
>> > associated with a website that we have no problem accessing. Only the
>> > "additional" IP address are giving us problems accessing.
>> >
>> > As part of our troubleshooting, I entered into the NIC card one of the
>> > IP
>> > addresses that we are having issues with as the primary IP address and
>> > that
>> > solved the issue. Again, it is only the additional IP address on the
>> > NIC
>> > that
>> > are causing problems.
>> >
>> > I can ping our DC from the IIS server and I can ping the main IP
>> > address
>> > of
>> > the IIS server from the DC, but when I ping one of the additional IP
>> > address
>> > of the IIS server from the DC, the first packet is received, but the
>> > next
>> > 75%
>> > are lost.
>> >
>> > Now here is where I am ignorant: why am I getting a different physical
>> > address for the additional IP addresses than the main IP address when I
>> > do
>> > an
>> > arp -a test? That seems very strange to me. Should there only be one
>> > physical
>> > address for one NIC card?
>> >
>> > Any help would be greatly appreciated.
>>
>>
>>