Windows Server 2003 Service Pack 1

Hello,
I have a machine running Windows Server 2003 and IIS 6.0 for Web and FTP
hosting. Last Friday I installed service pack 1 and connectivity stopped.
From inside my network i was able to access the ftp sites and the web sites
running on that machine and everything seemed ok. Coming back now on Monday
I have learned people outside our network canot access anything on that
machine. After some reading I found that SP1 installs the windows firewall,
thinking that it may be the problem I tried to check its settings only to
find that it was not running at all. I checked with our ISP and although
they too could not ping the address they did not show any problems with
their network. As a last ditch effort to at least get things back to a
running state I uninstalled service pack 1 and now everything is running
again.

Does anyone out there know any current issues with SP1 that may have
caused my problem or has anyone delt with this issue before and could offer
some advice?

--
-Scott

Thanks for the link. However, that really only confirmed what I already
knew and that is......many people are experiencing this same problem.
Like the people in that thread I too have 2 separate NICs connected to 2
separate LAN/WANs. One is connected to my internal network which uses my
internal DNS server address and one is my live IP which serves the web pages
and points to my ISPs DNS addresses. One thing I noticed about my problem
that was never mentioned in the thread is that IIS was serving the pages to
anyone on my local network. The problem occurred when someone NOT on my
local network tried to contact the site. It was because of this I figured
IIS was not the problem but was something occurring at the network level and
was blocking IPs. It was then I realized that SP1 installed a firewall but
that wasn't even activated. Just for giggles I activated it and looked at
its configuration and left it activated but turned off. Even still the
pages could be seen by only my local network and no one else. I am only
left to believe that SP1 installs some process that acts like a firewall and
blocks addresses that are more than 1 hop away from the machine.

-Scott

"me" <(E-Mail Removed)> wrote in message
news:513D5FB3-8CD9-4C8A-BB60-(E-Mail Removed)...
> Read the thread at
>
http://www.iis-resources.com/modules...er=ASC&start=0
>
> Let us know if you have multiple default gateways defined.
>
>
>
>
>
>
> "Scott Elgram" wrote:
>
> > Hello,
> > I have a machine running Windows Server 2003 and IIS 6.0 for Web and
FTP
> > hosting. Last Friday I installed service pack 1 and connectivity
stopped.
> > From inside my network i was able to access the ftp sites and the web
sites
> > running on that machine and everything seemed ok. Coming back now on
Monday
> > I have learned people outside our network canot access anything on that
> > machine. After some reading I found that SP1 installs the windows
firewall,
> > thinking that it may be the problem I tried to check its settings only
to
> > find that it was not running at all. I checked with our ISP and
although
> > they too could not ping the address they did not show any problems with
> > their network. As a last ditch effort to at least get things back to a
> > running state I uninstalled service pack 1 and now everything is running
> > again.
> >
> > Does anyone out there know any current issues with SP1 that may have
> > caused my problem or has anyone delt with this issue before and could
offer
> > some advice?
> >
> > --
> > -Scott
> >
> >
> >

I am having a similar problem and one other thing I noticed is that when the
issue is present (ie. you haven't rebooted or disabled and re-enabled the
adapter) the gateway disappears from the network configuration according to
'ipconfig /all' but all local subnet traffic functions as normal.


"Scott Elgram" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Thanks for the link. However, that really only confirmed what I
> already
> knew and that is......many people are experiencing this same problem.
> Like the people in that thread I too have 2 separate NICs connected to
> 2
> separate LAN/WANs. One is connected to my internal network which uses my
> internal DNS server address and one is my live IP which serves the web
> pages
> and points to my ISPs DNS addresses. One thing I noticed about my problem
> that was never mentioned in the thread is that IIS was serving the pages
> to
> anyone on my local network. The problem occurred when someone NOT on my
> local network tried to contact the site. It was because of this I figured
> IIS was not the problem but was something occurring at the network level
> and
> was blocking IPs. It was then I realized that SP1 installed a firewall
> but
> that wasn't even activated. Just for giggles I activated it and looked at
> its configuration and left it activated but turned off. Even still the
> pages could be seen by only my local network and no one else. I am only
> left to believe that SP1 installs some process that acts like a firewall
> and
> blocks addresses that are more than 1 hop away from the machine.
>
> -Scott
>
> "me" <(E-Mail Removed)> wrote in message
> news:513D5FB3-8CD9-4C8A-BB60-(E-Mail Removed)...
>> Read the thread at
>>
> http://www.iis-resources.com/modules...er=ASC&start=0
>>
>> Let us know if you have multiple default gateways defined.
>>
>>
>>
>>
>>
>>
>> "Scott Elgram" wrote:
>>
>> > Hello,
>> > I have a machine running Windows Server 2003 and IIS 6.0 for Web
>> > and
> FTP
>> > hosting. Last Friday I installed service pack 1 and connectivity
> stopped.
>> > From inside my network i was able to access the ftp sites and the web
> sites
>> > running on that machine and everything seemed ok. Coming back now on
> Monday
>> > I have learned people outside our network canot access anything on that
>> > machine. After some reading I found that SP1 installs the windows
> firewall,
>> > thinking that it may be the problem I tried to check its settings only
> to
>> > find that it was not running at all. I checked with our ISP and
> although
>> > they too could not ping the address they did not show any problems with
>> > their network. As a last ditch effort to at least get things back to a
>> > running state I uninstalled service pack 1 and now everything is
>> > running
>> > again.
>> >
>> > Does anyone out there know any current issues with SP1 that may
>> > have
>> > caused my problem or has anyone delt with this issue before and could
> offer
>> > some advice?
>> >
>> > --
>> > -Scott
>> >
>> >
>> >
>
>

I posted in the thread mentioned above that I too am experiencing this
problem but with the added twist that both of my NICs indeed use the
same gateway address which will hopefully start getting people away
from the idea that it can't work due to conflicting gateways...

Also, I have the same experience in that I can access the sites on the
local subnet but not from anywhere else. For now I am using the repair
connection option and it brings everything back online just fine.
Unfortunately, I need to do that way too often for it to be all that
useful.

Has anyone been able to get Microsoft to admit this is a problem and
that they are working on it? I'd rather not uninstall SP1 and then just
have to reinstall it again in a couple of days if they are indeed
working on a fix...

Preston,

Interesting note that ipconfig /all is showing the gateway as
non-existant while this problem is being experienced. Hopefully someone
at Microsoft will patch this up quickly...anyone wanna take bets?

Jer

My workaround (until acknowledged by Microsoft as a problem and a solution provided) is to use a scheduled batch file that uses the "repair feature". I was tired (and I do mean tired) of getting up anywhere from 1:00 am to 3:00 am just to repair the connection. My scheduled job runs for 8 hours daily beginning at 12:00 AM since this anomaly would occur anywhere in that timeframe.

My batch file does the following:
::Flushes the ARP cache.
arp -d *

::Flushes the NETBios cache.
nbtstat -R

::Flushes the DNS client resolver cache.
ipconfig /flushdns

::Reregisters with WINS.
nbtstat -RR

::Reregisters with DNS.
ipconfig /registerdns
***Just make sure your Domain Group Policy or Local Policy gives the user right "logon as a batch job" for the account issuing the scheduled job or use an account that has that right.***

Dennis,

I was running a very similar script...I got the idea from another
thread (not sure if it was you or someone else that suggested it).

Anyway, I was still losing connections way too often (as much as every
10 minutes). It was beyond annoying. Both of my IPs were on the same
subnet so I was able to move them onto just one NIC. Since then,
everything has been fine.

I still would like MS to release a hotfix to truly resolve the problem,
but at least for now my server is stable again.

I'm hoping someone will post back soon saying they've heard a fix is in
the works...

Jer