Strange behavior

I have a Windows 2003/SP1 server utilizing IIS 6. The server is dul-homed and its outward connection sporadically will not respond to pings. Initially I was rebooting the server and later by chance I just started using the Windows "repair feature" (refreshes network settings) which once that was done the nic would begin to respond on that interface.

I have beat my brains out on this for the last two weeks and would like to know if anyone else has experienced this anomaly?

We are having exact same problem on IIS 6 w/ SP1 on Dual-Homed server (2 NIC,
2 Subnets). We have been looking at issues for about 1 week, glad we're not
crazy -- this is definitely emerging as an issue for SP1.

REFERENCE:
Posting Catgory: IIS General
Search: SP1
Posting: 4/21/05 "IIS Problem after SP1 in windows 2003" by Carlos

REFERENCE: (our problem
http://www.iis-resources.com/modules...forumpost16979

This is our description of the same problem, originally posted on an IIS
Forum.

Thanks for the link and it was "fun" reading the thread. Your setup is EXACTLY how I have mine. I installed SP1 and a week later the outward connection started its flaking out. Just today it has done it 3 times. Have you worked out an interim solution?!?

I am going to build a script that mimic the "repair feature" so it will refresh the connection every hour to see if that helps.

Command Sequence for the Repair Command
Procedure sequence Command-line equivalent
1 Checks whether DHCP is enabled, and if it is, issues a broadcast renew to refresh the IP address. Performs similar to ipconfig /renew
(See Note below this table)

2 Flushes the ARP cache. arp -d *
3 Flushes the NETBios cache. nbtstat –R
4 Flushes the DNS client resolver cache. ipconfig /flushdns
5 Reregisters with WINS. nbtstat –RR
6 Reregisters with DNS. ipconfig /registerdns

Dennis:

You are RIGHT-ON with the automating the "repair" as a work-around. We have
not uninstalled SP1 as many others I've contacted have, because we want SP1
and we want it to work!

We're a Certified Partner, so I happened to goto a MS Partner function
yesterday and am already getting traction on escalation. I have gotten a
response from a Microsoft PSS engineer for IIS and am proceeding with
bringing this to the Microsoft PSS team for Windows Server. I should be
getting a free incident out of the deal... and hopefully we will get a Hotfix
or some kind of additional instruction / configuration tweak to support the
dual-home after SP1.

I started a new post: SP1 affect on Dual-Homed Servers (?)
Look for updates there...

Also, I'm sending you my ontact info if you want to contact me direct.

----------------------------------
"Dennis P. Smith" wrote:

> Thanks for the link and it was "fun" reading the thread. Your setup is EXACTLY how I have mine. I installed SP1 and a week later the outward connection started its flaking out. Just today it has done it 3 times. Have you worked out an interim solution?!?
>
> I am going to build a script that mimic the "repair feature" so it will refresh the connection every hour to see if that helps.
>
> Command Sequence for the Repair Command
> Procedure sequence Command-line equivalent
> 1 Checks whether DHCP is enabled, and if it is, issues a broadcast renew to refresh the IP address. Performs similar to ipconfig /renew
> (See Note below this table)
>
> 2 Flushes the ARP cache. arp -d *
> 3 Flushes the NETBios cache. nbtstat –R
> 4 Flushes the DNS client resolver cache. ipconfig /flushdns
> 5 Reregisters with WINS. nbtstat –RR
> 6 Reregisters with DNS. ipconfig /registerdns
>

Dennis or Arcanum BC:

Have either of you had success with automating the "repair" process? If so,
could you post the actual script used?


"ARCANUM BC" wrote:

> Dennis:
>
> You are RIGHT-ON with the automating the "repair" as a work-around. We have
> not uninstalled SP1 as many others I've contacted have, because we want SP1
> and we want it to work!
>
> We're a Certified Partner, so I happened to goto a MS Partner function
> yesterday and am already getting traction on escalation. I have gotten a
> response from a Microsoft PSS engineer for IIS and am proceeding with
> bringing this to the Microsoft PSS team for Windows Server. I should be
> getting a free incident out of the deal... and hopefully we will get a Hotfix
> or some kind of additional instruction / configuration tweak to support the
> dual-home after SP1.
>
> I started a new post: SP1 affect on Dual-Homed Servers (?)
> Look for updates there...
>
> Also, I'm sending you my ontact info if you want to contact me direct.
>
> ----------------------------------
> "Dennis P. Smith" wrote:
>
> > Thanks for the link and it was "fun" reading the thread. Your setup is EXACTLY how I have mine. I installed SP1 and a week later the outward connection started its flaking out. Just today it has done it 3 times. Have you worked out an interim solution?!?
> >
> > I am going to build a script that mimic the "repair feature" so it will refresh the connection every hour to see if that helps.
> >
> > Command Sequence for the Repair Command
> > Procedure sequence Command-line equivalent
> > 1 Checks whether DHCP is enabled, and if it is, issues a broadcast renew to refresh the IP address. Performs similar to ipconfig /renew
> > (See Note below this table)
> >
> > 2 Flushes the ARP cache. arp -d *
> > 3 Flushes the NETBios cache. nbtstat –R
> > 4 Flushes the DNS client resolver cache. ipconfig /flushdns
> > 5 Reregisters with WINS. nbtstat –RR
> > 6 Reregisters with DNS. ipconfig /registerdns
> >

Create a batch file
My batch file does the following:
::::::::::::::::Begin copy below this line::::::::::::::::
::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
::::::::::::::::End copy above this line::::::::::::::::


***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 P. Smith" wrote:
>>
>> > Thanks for the link and it was "fun" reading the thread. Your setup is
>> > EXACTLY how I have mine. I installed SP1 and a week later the outward
>> > connection started its flaking out. Just today it has done it 3 times.
>> > Have you worked out an interim solution?!?
>> >
>> > I am going to build a script that mimic the "repair feature" so it will
>> > refresh the connection every hour to see if that helps.
>> >
>> > Command Sequence for the Repair Command
>> > Procedure sequence Command-line equivalent
>> > 1 Checks whether DHCP is enabled, and if it is, issues a
>> > broadcast renew to refresh the IP address. Performs similar to ipconfig
>> > /renew
>> > (See Note below this table)
>> >
>> > 2 Flushes the ARP cache. arp -d *
>> > 3 Flushes the NETBios cache. nbtstat -R
>> > 4 Flushes the DNS client resolver cache. ipconfig /flushdns
>> > 5 Reregisters with WINS. nbtstat -RR
>> > 6 Reregisters with DNS. ipconfig /registerdns
>> >