OK, I have looked through several threads and can't quite find the answers
that fit my problems. If they are already here, please let me know where to
find them.

Here's the problem.

On one machine I have 2003 Server with SP1 (I know that SP1 seems to be
some, if not all of the problem, but I really don't want to have to uninstall
it)

On this machine I have 2 NICs. One is a hardcoded address going through my
DSL and the other is a dynamic address (192.168.x.y network)

Every so often, and it does not seem to be a fixed amount of time, the DSL
address refuses to accept connections and no one can connect to that server
from the Internet.

Currently when that happens I just remote desktop into the system through
local network and disable, then re-enable the DSL NIC and everything comes
back up.

I figured that the NIC was bad, so I replaced it. Within a day I had the
same problem with the new NIC. So I swapped network cables between the 2 NICs
and reassigned the addresses. Then within a day or so I had the same problem
on the other NIC. This NIC had NEVER gone down for the local network but now
goes down just as often as the DSL NIC used to.

Now I have a new machine. I just installed Win2003 server with SP1 and this
machine is a similar setup. I run into the same problem. Only with this
machine I MUST reboot to get the system back up. The other odd thing about
this machine is that when I ping the DSL address from inside my building (So
the traffic only goes through my switch) I get a pong back. But if I try to
ping from outside the building (I LOVE remote desktop!!!) then I can not ping
the system. Once I reboot the machine I can do everything for inside or
outside.

So I figure these 2 machines are related in thier problems, but I have no
clue what to do. My Win2000 server is running without a problem and I have
been tempted to install that on all my web srevers.

So does anyone have a definitive answer how to fix this? I guess I can
uninstall SP1 if I need to, but I hope there is something else that will fix
this.

Yes, I have validated the Firewall. Again things work after either rebooting
the one machine or resetting the NIC on the other. THen things will work for
a while and then quit working again.

Thanks,
Mike

Your issue seems to be related to basic networking and not IIS6.

I doubt the issue is Windows Server 2003 SP1 because many other people run
with dual NICs without issues. I suspect it is some non-obvious
misconfiguration, and we'll just have to troubleshoot to figure it out.

If I had to choose between Windows 2000 and Windows Server 2003, I will
always choose Windows Server 2003. You just start off on a better footing on
so many levels that you should invest a little time to figure out what is
going awry.

> On this machine I have 2 NICs. One is a hardcoded address going through
> my DSL and the other is a dynamic address (192.168.x.y network)
Your network topology is not clear to me. Can you describe it better.

Are you saying the machine has two NICs. One of the NIC has an Ethernet
cable directly into your DSL Modem and the TCP/IP binding of this NIC is
hardcoded to be publicly addressable. The other NIC is plugged into your
internal network, and its TCP/IP binding has it obtaining an IP from a DHCP
server running on that internal network.


It almost sounds like your dual-homed machine is just not configured
correctly (I'm no networking expert so I cannot go further) and that after
some "time-out" Windows is reverting behavior back to something else which
is not dual-homed. So your job is to figure out the right way to configure
this dual-homed server...

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Mike Collins" <MikeCollins [at] discussions.microsoft.com> wrote in message
news:08129FED-889C-4E20-B91E-1537C4044627 [at] microsoft.com...
OK, I have looked through several threads and can't quite find the answers
that fit my problems. If they are already here, please let me know where to
find them.

Here's the problem.

On one machine I have 2003 Server with SP1 (I know that SP1 seems to be
some, if not all of the problem, but I really don't want to have to
uninstall
it)

On this machine I have 2 NICs. One is a hardcoded address going through my
DSL and the other is a dynamic address (192.168.x.y network)

Every so often, and it does not seem to be a fixed amount of time, the DSL
address refuses to accept connections and no one can connect to that server
from the Internet.

Currently when that happens I just remote desktop into the system through
local network and disable, then re-enable the DSL NIC and everything comes
back up.

I figured that the NIC was bad, so I replaced it. Within a day I had the
same problem with the new NIC. So I swapped network cables between the 2
NICs
and reassigned the addresses. Then within a day or so I had the same problem
on the other NIC. This NIC had NEVER gone down for the local network but now
goes down just as often as the DSL NIC used to.

Now I have a new machine. I just installed Win2003 server with SP1 and this
machine is a similar setup. I run into the same problem. Only with this
machine I MUST reboot to get the system back up. The other odd thing about
this machine is that when I ping the DSL address from inside my building (So
the traffic only goes through my switch) I get a pong back. But if I try to
ping from outside the building (I LOVE remote desktop!!!) then I can not
ping
the system. Once I reboot the machine I can do everything for inside or
outside.

So I figure these 2 machines are related in thier problems, but I have no
clue what to do. My Win2000 server is running without a problem and I have
been tempted to install that on all my web srevers.

So does anyone have a definitive answer how to fix this? I guess I can
uninstall SP1 if I need to, but I hope there is something else that will fix
this.

Yes, I have validated the Firewall. Again things work after either rebooting
the one machine or resetting the NIC on the other. THen things will work for
a while and then quit working again.

Thanks,
Mike

What kind of information would I need to provide for you.

But before I do let me tell you what I have done.

On one machine (the one I needed to reboot) I uninstalled SP1. That machine
has not gone down since then. (Almost 24 hours now)

The other machine has gone down twice since then. At least I have remote
desktop so I can reset the NIC.

I have been looking for 2 days and I have seen hundreds of people stating
that ever since they installed SP1 they were seeing similar problems. Every
one of these people that indicated that they uninstalled SP1 said that their
problems went away. So I tried uninstalling that on machine. Since I am
seeing good results without SP1 on the one machine I have to ask if that was
the problem.

Of course 1 day of no lockups is not a ver good indicator, so I need to keep
looking for a few days and report back then. If the Non-SP1 machine continues
to work and the SP1 machine does not, then I will uninstall from the other
machine as well.

Interestingly enough I have a third machine. But it is only on an internal
network. I have a router/firewall that protects that server and I just allow
port 80 to redirect to that machine. (Also with SP1) and it has never had
this problem. Though that machine only has 1 NIC and only has 1 DHCP IP
address.

So it looks like this problem is only related to machines outside of my
local network and only with SP1 loaded.

Thanks for your help so far. If I ever figure this out I will post my
results to all the Forums I have been browsing.

Mike Collins

"David Wang [Msft]" wrote:

> Your issue seems to be related to basic networking and not IIS6.
>
> I doubt the issue is Windows Server 2003 SP1 because many other people run
> with dual NICs without issues. I suspect it is some non-obvious
> misconfiguration, and we'll just have to troubleshoot to figure it out.
>
> If I had to choose between Windows 2000 and Windows Server 2003, I will
> always choose Windows Server 2003. You just start off on a better footing on
> so many levels that you should invest a little time to figure out what is
> going awry.
>
> > On this machine I have 2 NICs. One is a hardcoded address going through
> > my DSL and the other is a dynamic address (192.168.x.y network)
> Your network topology is not clear to me. Can you describe it better.
>
> Are you saying the machine has two NICs. One of the NIC has an Ethernet
> cable directly into your DSL Modem and the TCP/IP binding of this NIC is
> hardcoded to be publicly addressable. The other NIC is plugged into your
> internal network, and its TCP/IP binding has it obtaining an IP from a DHCP
> server running on that internal network.
>
>
> It almost sounds like your dual-homed machine is just not configured
> correctly (I'm no networking expert so I cannot go further) and that after
> some "time-out" Windows is reverting behavior back to something else which
> is not dual-homed. So your job is to figure out the right way to configure
> this dual-homed server...
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no rights.
> //
> "Mike Collins" <MikeCollins [at] discussions.microsoft.com> wrote in message
> news:08129FED-889C-4E20-B91E-1537C4044627 [at] microsoft.com...
> OK, I have looked through several threads and can't quite find the answers
> that fit my problems. If they are already here, please let me know where to
> find them.
>
> Here's the problem.
>
> On one machine I have 2003 Server with SP1 (I know that SP1 seems to be
> some, if not all of the problem, but I really don't want to have to
> uninstall
> it)
>
> On this machine I have 2 NICs. One is a hardcoded address going through my
> DSL and the other is a dynamic address (192.168.x.y network)
>
> Every so often, and it does not seem to be a fixed amount of time, the DSL
> address refuses to accept connections and no one can connect to that server
> from the Internet.
>
> Currently when that happens I just remote desktop into the system through
> local network and disable, then re-enable the DSL NIC and everything comes
> back up.
>
> I figured that the NIC was bad, so I replaced it. Within a day I had the
> same problem with the new NIC. So I swapped network cables between the 2
> NICs
> and reassigned the addresses. Then within a day or so I had the same problem
> on the other NIC. This NIC had NEVER gone down for the local network but now
> goes down just as often as the DSL NIC used to.
>
> Now I have a new machine. I just installed Win2003 server with SP1 and this
> machine is a similar setup. I run into the same problem. Only with this
> machine I MUST reboot to get the system back up. The other odd thing about
> this machine is that when I ping the DSL address from inside my building (So
> the traffic only goes through my switch) I get a pong back. But if I try to
> ping from outside the building (I LOVE remote desktop!!!) then I can not
> ping
> the system. Once I reboot the machine I can do everything for inside or
> outside.
>
> So I figure these 2 machines are related in thier problems, but I have no
> clue what to do. My Win2000 server is running without a problem and I have
> been tempted to install that on all my web srevers.
>
> So does anyone have a definitive answer how to fix this? I guess I can
> uninstall SP1 if I need to, but I hope there is something else that will fix
> this.
>
> Yes, I have validated the Firewall. Again things work after either rebooting
> the one machine or resetting the NIC on the other. THen things will work for
> a while and then quit working again.
>
> Thanks,
> Mike
>
>
>

OK I found the solution.
KB article which helps:
http://support.microsoft.com/kb/898060/

On my machines with SP1 I installed this patch and have not had a problem
for almost two weeks.

So I am pretty sure this is the fix.

I would assume that Microsoft would want to put this into the Automatic
Updates so that anyone with 2003 Server SP1 would get the fix.

If not, at least I have found the solution for my netowrking problem.


"Mike Collins" wrote:

> What kind of information would I need to provide for you.
>
> But before I do let me tell you what I have done.
>
> On one machine (the one I needed to reboot) I uninstalled SP1. That machine
> has not gone down since then. (Almost 24 hours now)
>
> The other machine has gone down twice since then. At least I have remote
> desktop so I can reset the NIC.
>
> I have been looking for 2 days and I have seen hundreds of people stating
> that ever since they installed SP1 they were seeing similar problems. Every
> one of these people that indicated that they uninstalled SP1 said that their
> problems went away. So I tried uninstalling that on machine. Since I am
> seeing good results without SP1 on the one machine I have to ask if that was
> the problem.
>
> Of course 1 day of no lockups is not a ver good indicator, so I need to keep
> looking for a few days and report back then. If the Non-SP1 machine continues
> to work and the SP1 machine does not, then I will uninstall from the other
> machine as well.
>
> Interestingly enough I have a third machine. But it is only on an internal
> network. I have a router/firewall that protects that server and I just allow
> port 80 to redirect to that machine. (Also with SP1) and it has never had
> this problem. Though that machine only has 1 NIC and only has 1 DHCP IP
> address.
>
> So it looks like this problem is only related to machines outside of my
> local network and only with SP1 loaded.
>
> Thanks for your help so far. If I ever figure this out I will post my
> results to all the Forums I have been browsing.
>
> Mike Collins
>
> "David Wang [Msft]" wrote:
>
> > Your issue seems to be related to basic networking and not IIS6.
> >
> > I doubt the issue is Windows Server 2003 SP1 because many other people run
> > with dual NICs without issues. I suspect it is some non-obvious
> > misconfiguration, and we'll just have to troubleshoot to figure it out.
> >
> > If I had to choose between Windows 2000 and Windows Server 2003, I will
> > always choose Windows Server 2003. You just start off on a better footing on
> > so many levels that you should invest a little time to figure out what is
> > going awry.
> >
> > > On this machine I have 2 NICs. One is a hardcoded address going through
> > > my DSL and the other is a dynamic address (192.168.x.y network)
> > Your network topology is not clear to me. Can you describe it better.
> >
> > Are you saying the machine has two NICs. One of the NIC has an Ethernet
> > cable directly into your DSL Modem and the TCP/IP binding of this NIC is
> > hardcoded to be publicly addressable. The other NIC is plugged into your
> > internal network, and its TCP/IP binding has it obtaining an IP from a DHCP
> > server running on that internal network.
> >
> >
> > It almost sounds like your dual-homed machine is just not configured
> > correctly (I'm no networking expert so I cannot go further) and that after
> > some "time-out" Windows is reverting behavior back to something else which
> > is not dual-homed. So your job is to figure out the right way to configure
> > this dual-homed server...
> >
> > --
> > //David
> > IIS
> > http://blogs.msdn.com/David.Wang
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > //
> > "Mike Collins" <MikeCollins [at] discussions.microsoft.com> wrote in message
> > news:08129FED-889C-4E20-B91E-1537C4044627 [at] microsoft.com...
> > OK, I have looked through several threads and can't quite find the answers
> > that fit my problems. If they are already here, please let me know where to
> > find them.
> >
> > Here's the problem.
> >
> > On one machine I have 2003 Server with SP1 (I know that SP1 seems to be
> > some, if not all of the problem, but I really don't want to have to
> > uninstall
> > it)
> >
> > On this machine I have 2 NICs. One is a hardcoded address going through my
> > DSL and the other is a dynamic address (192.168.x.y network)
> >
> > Every so often, and it does not seem to be a fixed amount of time, the DSL
> > address refuses to accept connections and no one can connect to that server
> > from the Internet.
> >
> > Currently when that happens I just remote desktop into the system through
> > local network and disable, then re-enable the DSL NIC and everything comes
> > back up.
> >
> > I figured that the NIC was bad, so I replaced it. Within a day I had the
> > same problem with the new NIC. So I swapped network cables between the 2
> > NICs
> > and reassigned the addresses. Then within a day or so I had the same problem
> > on the other NIC. This NIC had NEVER gone down for the local network but now
> > goes down just as often as the DSL NIC used to.
> >
> > Now I have a new machine. I just installed Win2003 server with SP1 and this
> > machine is a similar setup. I run into the same problem. Only with this
> > machine I MUST reboot to get the system back up. The other odd thing about
> > this machine is that when I ping the DSL address from inside my building (So
> > the traffic only goes through my switch) I get a pong back. But if I try to
> > ping from outside the building (I LOVE remote desktop!!!) then I can not
> > ping
> > the system. Once I reboot the machine I can do everything for inside or
> > outside.
> >
> > So I figure these 2 machines are related in thier problems, but I have no
> > clue what to do. My Win2000 server is running without a problem and I have
> > been tempted to install that on all my web srevers.
> >
> > So does anyone have a definitive answer how to fix this? I guess I can
> > uninstall SP1 if I need to, but I hope there is something else that will fix
> > this.
> >
> > Yes, I have validated the Firewall. Again things work after either rebooting
> > the one machine or resetting the NIC on the other. THen things will work for
> > a while and then quit working again.
> >
> > Thanks,
> > Mike
> >
> >
> >

BUMMER!!!

The problem is now back again. The patch worked for about a month and is not
doing the exact same thing again.

Anyone else with any ideas?

"Mike Collins" wrote:

> OK I found the solution.
> KB article which helps:
> http://support.microsoft.com/kb/898060/
>
> On my machines with SP1 I installed this patch and have not had a problem
> for almost two weeks.
>
> So I am pretty sure this is the fix.
>
> I would assume that Microsoft would want to put this into the Automatic
> Updates so that anyone with 2003 Server SP1 would get the fix.
>
> If not, at least I have found the solution for my netowrking problem.
>
>
> "Mike Collins" wrote:
>
> > What kind of information would I need to provide for you.
> >
> > But before I do let me tell you what I have done.
> >
> > On one machine (the one I needed to reboot) I uninstalled SP1. That machine
> > has not gone down since then. (Almost 24 hours now)
> >
> > The other machine has gone down twice since then. At least I have remote
> > desktop so I can reset the NIC.
> >
> > I have been looking for 2 days and I have seen hundreds of people stating
> > that ever since they installed SP1 they were seeing similar problems. Every
> > one of these people that indicated that they uninstalled SP1 said that their
> > problems went away. So I tried uninstalling that on machine. Since I am
> > seeing good results without SP1 on the one machine I have to ask if that was
> > the problem.
> >
> > Of course 1 day of no lockups is not a ver good indicator, so I need to keep
> > looking for a few days and report back then. If the Non-SP1 machine continues
> > to work and the SP1 machine does not, then I will uninstall from the other
> > machine as well.
> >
> > Interestingly enough I have a third machine. But it is only on an internal
> > network. I have a router/firewall that protects that server and I just allow
> > port 80 to redirect to that machine. (Also with SP1) and it has never had
> > this problem. Though that machine only has 1 NIC and only has 1 DHCP IP
> > address.
> >
> > So it looks like this problem is only related to machines outside of my
> > local network and only with SP1 loaded.
> >
> > Thanks for your help so far. If I ever figure this out I will post my
> > results to all the Forums I have been browsing.
> >
> > Mike Collins
> >
> > "David Wang [Msft]" wrote:
> >
> > > Your issue seems to be related to basic networking and not IIS6.
> > >
> > > I doubt the issue is Windows Server 2003 SP1 because many other people run
> > > with dual NICs without issues. I suspect it is some non-obvious
> > > misconfiguration, and we'll just have to troubleshoot to figure it out.
> > >
> > > If I had to choose between Windows 2000 and Windows Server 2003, I will
> > > always choose Windows Server 2003. You just start off on a better footing on
> > > so many levels that you should invest a little time to figure out what is
> > > going awry.
> > >
> > > > On this machine I have 2 NICs. One is a hardcoded address going through
> > > > my DSL and the other is a dynamic address (192.168.x.y network)
> > > Your network topology is not clear to me. Can you describe it better.
> > >
> > > Are you saying the machine has two NICs. One of the NIC has an Ethernet
> > > cable directly into your DSL Modem and the TCP/IP binding of this NIC is
> > > hardcoded to be publicly addressable. The other NIC is plugged into your
> > > internal network, and its TCP/IP binding has it obtaining an IP from a DHCP
> > > server running on that internal network.
> > >
> > >
> > > It almost sounds like your dual-homed machine is just not configured
> > > correctly (I'm no networking expert so I cannot go further) and that after
> > > some "time-out" Windows is reverting behavior back to something else which
> > > is not dual-homed. So your job is to figure out the right way to configure
> > > this dual-homed server...
> > >
> > > --
> > > //David
> > > IIS
> > > http://blogs.msdn.com/David.Wang
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > //
> > > "Mike Collins" <MikeCollins [at] discussions.microsoft.com> wrote in message
> > > news:08129FED-889C-4E20-B91E-1537C4044627 [at] microsoft.com...
> > > OK, I have looked through several threads and can't quite find the answers
> > > that fit my problems. If they are already here, please let me know where to
> > > find them.
> > >
> > > Here's the problem.
> > >
> > > On one machine I have 2003 Server with SP1 (I know that SP1 seems to be
> > > some, if not all of the problem, but I really don't want to have to
> > > uninstall
> > > it)
> > >
> > > On this machine I have 2 NICs. One is a hardcoded address going through my
> > > DSL and the other is a dynamic address (192.168.x.y network)
> > >
> > > Every so often, and it does not seem to be a fixed amount of time, the DSL
> > > address refuses to accept connections and no one can connect to that server
> > > from the Internet.
> > >
> > > Currently when that happens I just remote desktop into the system through
> > > local network and disable, then re-enable the DSL NIC and everything comes
> > > back up.
> > >
> > > I figured that the NIC was bad, so I replaced it. Within a day I had the
> > > same problem with the new NIC. So I swapped network cables between the 2
> > > NICs
> > > and reassigned the addresses. Then within a day or so I had the same problem
> > > on the other NIC. This NIC had NEVER gone down for the local network but now
> > > goes down just as often as the DSL NIC used to.
> > >
> > > Now I have a new machine. I just installed Win2003 server with SP1 and this
> > > machine is a similar setup. I run into the same problem. Only with this
> > > machine I MUST reboot to get the system back up. The other odd thing about
> > > this machine is that when I ping the DSL address from inside my building (So
> > > the traffic only goes through my switch) I get a pong back. But if I try to
> > > ping from outside the building (I LOVE remote desktop!!!) then I can not
> > > ping
> > > the system. Once I reboot the machine I can do everything for inside or
> > > outside.
> > >
> > > So I figure these 2 machines are related in thier problems, but I have no
> > > clue what to do. My Win2000 server is running without a problem and I have
> > > been tempted to install that on all my web srevers.
> > >
> > > So does anyone have a definitive answer how to fix this? I guess I can
> > > uninstall SP1 if I need to, but I hope there is something else that will fix
> > > this.
> > >
> > > Yes, I have validated the Firewall. Again things work after either rebooting
> > > the one machine or resetting the NIC on the other. THen things will work for
> > > a while and then quit working again.
> > >
> > > Thanks,
> > > Mike
> > >
> > >
> > >