Hello
I have a vague problem raised to me by a client that I would throw out there
and see what comes back. I do not have immediate access to the machine to
test anything so when I do get the opportunity, I would like to have
something prepared....
They have a multihomed Windows 2000 IIS server with 2 NICs with different IP
addresses on the same subnet (yuck I know, not recommended). I should note
that this web server also has RAS installed with a range of static routes.
1 NIC is for internet client traffic and the other NIC is for internal
company network traffic. There are static routes configured on the external
NIC to route traffic accordingly.
Apparently when the server is rebooted, internal company network clients can
access the web server via either ip address but external (internet) clients
cannot access it at all. The client rep told me that he went into the TPPIP
properties for the external NIC, altered the IP address to something else,
hit apply, and then altered it back to the original IP address. He then
discovered that external clients could now connect fine.
The behaviour can be reproduced upon a reboot apparently. Can anyone suggest
what is causing this and a possible fix? If no solution, what steps would
you suggest I take to troubleshoot the issue? Its kinda like TCPIP is
getting confused when the server starts up and needs to be refreshed to
behave properly.
Regards,
Damon
|
Similar Threads
Linear Mode
