ICW is only a temp fix

W2k3 (non R2) inst in 04, no recent hardware changes, only new sw is updates,
single NIC

Weird problem is that Exchange stops receiving/sending external mail
(services are still running fine so internal works) and external RDC
connections fail (internal connections still work fine)

Running ICW fixes problem for a short time (20 to 40 minutes). Exchange
sends and receives and a remote RDC can connect.

If a RDC is made and left running, the amount of time before loss of
connection occurs can be extended for hours.

In any case, browsing works all the time. Thanks in advance.

Cliff
Tue May 13 11:59:13 PDT 2008

How is it connected to the net?

-Cliff


"Dane" <Dane@discussions.microsoft.com> wrote in message
news:2B1855F1-777C-425B-9DD5-0F4811CB6FC5@microsoft.com...
> W2k3 (non R2) inst in 04, no recent hardware changes, only new sw is
> updates,
> single NIC
>
> Weird problem is that Exchange stops receiving/sending external mail
> (services are still running fine so internal works) and external RDC
> connections fail (internal connections still work fine)
>
> Running ICW fixes problem for a short time (20 to 40 minutes). Exchange
> sends and receives and a remote RDC can connect.
>
> If a RDC is made and left running, the amount of time before loss of
> connection occurs can be extended for hours.
>
> In any case, browsing works all the time. Thanks in advance.
>
>

Dane
Tue May 13 12:35:06 PDT 2008

Single NIC thru DSL router (Actiontec701) Static IP

"Cliff Galiher" wrote:

> How is it connected to the net?
>
> -Cliff
>
>
> "Dane" <Dane@discussions.microsoft.com> wrote in message
> news:2B1855F1-777C-425B-9DD5-0F4811CB6FC5@microsoft.com...
> > W2k3 (non R2) inst in 04, no recent hardware changes, only new sw is
> > updates,
> > single NIC
> >
> > Weird problem is that Exchange stops receiving/sending external mail
> > (services are still running fine so internal works) and external RDC
> > connections fail (internal connections still work fine)
> >
> > Running ICW fixes problem for a short time (20 to 40 minutes). Exchange
> > sends and receives and a remote RDC can connect.
> >
> > If a RDC is made and left running, the amount of time before loss of
> > connection occurs can be extended for hours.
> >
> > In any case, browsing works all the time. Thanks in advance.
> >
> >
>

Cliff
Tue May 13 14:51:04 PDT 2008

Yeah, that is probably your problem. Actiontec makes a *decent* DSL
gateway, but their routing software sucks. You would be best served by
putting it in bridged mode and passing all traffic to a business class
firewall appliance. Sonicwall, watchguard, etc make devices or the SMB
market that all serve well and will protect your server substantially better
than the built-in actiontec and not seize with multiple connections.

-Cliff


"Dane" <Dane@discussions.microsoft.com> wrote in message
news:F3D1DA0D-FD16-4E73-800C-96EE23128DE9@microsoft.com...
> Single NIC thru DSL router (Actiontec701) Static IP
>
> "Cliff Galiher" wrote:
>
>> How is it connected to the net?
>>
>> -Cliff
>>
>>
>> "Dane" <Dane@discussions.microsoft.com> wrote in message
>> news:2B1855F1-777C-425B-9DD5-0F4811CB6FC5@microsoft.com...
>> > W2k3 (non R2) inst in 04, no recent hardware changes, only new sw is
>> > updates,
>> > single NIC
>> >
>> > Weird problem is that Exchange stops receiving/sending external mail
>> > (services are still running fine so internal works) and external RDC
>> > connections fail (internal connections still work fine)
>> >
>> > Running ICW fixes problem for a short time (20 to 40 minutes). Exchange
>> > sends and receives and a remote RDC can connect.
>> >
>> > If a RDC is made and left running, the amount of time before loss of
>> > connection occurs can be extended for hours.
>> >
>> > In any case, browsing works all the time. Thanks in advance.
>> >
>> >
>>

Dane
Tue May 13 15:06:01 PDT 2008


Thanks, but how does that address the fact that, if I force the addidional
connection via and external RDC connection (increasing the connection "load")
the connection is more reliable.

"Cliff Galiher" wrote:

> Yeah, that is probably your problem. Actiontec makes a *decent* DSL
> gateway, but their routing software sucks. You would be best served by
> putting it in bridged mode and passing all traffic to a business class
> firewall appliance. Sonicwall, watchguard, etc make devices or the SMB
> market that all serve well and will protect your server substantially better
> than the built-in actiontec and not seize with multiple connections.
>
> -Cliff
>
>
> "Dane" <Dane@discussions.microsoft.com> wrote in message
> news:F3D1DA0D-FD16-4E73-800C-96EE23128DE9@microsoft.com...
> > Single NIC thru DSL router (Actiontec701) Static IP
> >
> > "Cliff Galiher" wrote:
> >
> >> How is it connected to the net?
> >>
> >> -Cliff
> >>
> >>
> >> "Dane" <Dane@discussions.microsoft.com> wrote in message
> >> news:2B1855F1-777C-425B-9DD5-0F4811CB6FC5@microsoft.com...
> >> > W2k3 (non R2) inst in 04, no recent hardware changes, only new sw is
> >> > updates,
> >> > single NIC
> >> >
> >> > Weird problem is that Exchange stops receiving/sending external mail
> >> > (services are still running fine so internal works) and external RDC
> >> > connections fail (internal connections still work fine)
> >> >
> >> > Running ICW fixes problem for a short time (20 to 40 minutes). Exchange
> >> > sends and receives and a remote RDC can connect.
> >> >
> >> > If a RDC is made and left running, the amount of time before loss of
> >> > connection occurs can be extended for hours.
> >> >
> >> > In any case, browsing works all the time. Thanks in advance.
> >> >
> >> >
> >>
>

Merv
Tue May 13 15:30:59 PDT 2008

May be a power management problem with the NIC or a configuration issue.
May want to install and run a scan with the SBS 2003 BPA.

Microsoft Windows Small Business Server 2003 Best Practices Analyzer
http://207.46.19.190/downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

Small Business Server 2003 Best Practices Analyzer Updated
http://207.46.19.190/downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

How to Use the Windows SBS 2003 BPA
http://blogs.technet.com/sbs/archive/2007/10/22/how-to-use-the-windows-sbs-2003-bpa.aspx

--
Merv Porter [SBS-MVP]
============================

"Dane" <Dane@discussions.microsoft.com> wrote in message
news:9D0E31F5-2A9A-4665-9D05-210ECEBC7679@microsoft.com...
> Thanks, but how does that address the fact that, if I force the addidional
> connection via and external RDC connection (increasing the connection
> "load")
> the connection is more reliable.
>
> "Cliff Galiher" wrote:
>
>> Yeah, that is probably your problem. Actiontec makes a *decent* DSL
>> gateway, but their routing software sucks. You would be best served by
>> putting it in bridged mode and passing all traffic to a business class
>> firewall appliance. Sonicwall, watchguard, etc make devices or the SMB
>> market that all serve well and will protect your server substantially
>> better
>> than the built-in actiontec and not seize with multiple connections.
>>
>> -Cliff
>>
>>
>> "Dane" <Dane@discussions.microsoft.com> wrote in message
>> news:F3D1DA0D-FD16-4E73-800C-96EE23128DE9@microsoft.com...
>> > Single NIC thru DSL router (Actiontec701) Static IP
>> >
>> > "Cliff Galiher" wrote:
>> >
>> >> How is it connected to the net?
>> >>
>> >> -Cliff
>> >>
>> >>
>> >> "Dane" <Dane@discussions.microsoft.com> wrote in message
>> >> news:2B1855F1-777C-425B-9DD5-0F4811CB6FC5@microsoft.com...
>> >> > W2k3 (non R2) inst in 04, no recent hardware changes, only new sw is
>> >> > updates,
>> >> > single NIC
>> >> >
>> >> > Weird problem is that Exchange stops receiving/sending external mail
>> >> > (services are still running fine so internal works) and external RDC
>> >> > connections fail (internal connections still work fine)
>> >> >
>> >> > Running ICW fixes problem for a short time (20 to 40 minutes).
>> >> > Exchange
>> >> > sends and receives and a remote RDC can connect.
>> >> >
>> >> > If a RDC is made and left running, the amount of time before loss of
>> >> > connection occurs can be extended for hours.
>> >> >
>> >> > In any case, browsing works all the time. Thanks in advance.
>> >> >
>> >> >
>> >>
>>

Cliff
Tue May 13 16:10:39 PDT 2008

It doesn't increase the connection load. It is a single, stationary
connection that the actiontec stack prioritizes (because it is active.)
Without that active connection, nothing gets particularly prioritized, so
every syn/ack adds another one to the pile that the actiontec (improperly)
tracks and eventually crashes its poor little OS. It is just a poor IP
stack that mismanages its own resources. The fact that, as you said, you
can continue to access internally, seems to indicate it is not SBS at all,
but the router that quits getting traffic to the box.

I understand the reluctance to throw money at the problem without proof, so
if you have a spare consumer router around (linksys, netgear, etc) then you
can even throw THAT on between the actiontec and SBS, still putting the
actiontec in gateway mode. See if that resolves the problem....

-Cliff


"Dane" <Dane@discussions.microsoft.com> wrote in message
news:9D0E31F5-2A9A-4665-9D05-210ECEBC7679@microsoft.com...
> Thanks, but how does that address the fact that, if I force the addidional
> connection via and external RDC connection (increasing the connection
> "load")
> the connection is more reliable.
>
> "Cliff Galiher" wrote:
>
>> Yeah, that is probably your problem. Actiontec makes a *decent* DSL
>> gateway, but their routing software sucks. You would be best served by
>> putting it in bridged mode and passing all traffic to a business class
>> firewall appliance. Sonicwall, watchguard, etc make devices or the SMB
>> market that all serve well and will protect your server substantially
>> better
>> than the built-in actiontec and not seize with multiple connections.
>>
>> -Cliff
>>
>>
>> "Dane" <Dane@discussions.microsoft.com> wrote in message
>> news:F3D1DA0D-FD16-4E73-800C-96EE23128DE9@microsoft.com...
>> > Single NIC thru DSL router (Actiontec701) Static IP
>> >
>> > "Cliff Galiher" wrote:
>> >
>> >> How is it connected to the net?
>> >>
>> >> -Cliff
>> >>
>> >>
>> >> "Dane" <Dane@discussions.microsoft.com> wrote in message
>> >> news:2B1855F1-777C-425B-9DD5-0F4811CB6FC5@microsoft.com...
>> >> > W2k3 (non R2) inst in 04, no recent hardware changes, only new sw is
>> >> > updates,
>> >> > single NIC
>> >> >
>> >> > Weird problem is that Exchange stops receiving/sending external mail
>> >> > (services are still running fine so internal works) and external RDC
>> >> > connections fail (internal connections still work fine)
>> >> >
>> >> > Running ICW fixes problem for a short time (20 to 40 minutes).
>> >> > Exchange
>> >> > sends and receives and a remote RDC can connect.
>> >> >
>> >> > If a RDC is made and left running, the amount of time before loss of
>> >> > connection occurs can be extended for hours.
>> >> >
>> >> > In any case, browsing works all the time. Thanks in advance.
>> >> >
>> >> >
>> >>
>>

Dane
Thu May 15 15:17:00 PDT 2008

Thanks to both. Ran the analyzer. It indicated a couple of obscure items. The
one that seems to have fixed the issue was the recommendtion to create a
registry entry to disable EDNS connection. Server has been running for almost
48 hours without connection problem for either rdc or email.

"Cliff Galiher" wrote:

> It doesn't increase the connection load. It is a single, stationary
> connection that the actiontec stack prioritizes (because it is active.)
> Without that active connection, nothing gets particularly prioritized, so
> every syn/ack adds another one to the pile that the actiontec (improperly)
> tracks and eventually crashes its poor little OS. It is just a poor IP
> stack that mismanages its own resources. The fact that, as you said, you
> can continue to access internally, seems to indicate it is not SBS at all,
> but the router that quits getting traffic to the box.
>
> I understand the reluctance to throw money at the problem without proof, so
> if you have a spare consumer router around (linksys, netgear, etc) then you
> can even throw THAT on between the actiontec and SBS, still putting the
> actiontec in gateway mode. See if that resolves the problem....
>
> -Cliff
>
>
> "Dane" <Dane@discussions.microsoft.com> wrote in message
> news:9D0E31F5-2A9A-4665-9D05-210ECEBC7679@microsoft.com...
> > Thanks, but how does that address the fact that, if I force the addidional
> > connection via and external RDC connection (increasing the connection
> > "load")
> > the connection is more reliable.
> >
> > "Cliff Galiher" wrote:
> >
> >> Yeah, that is probably your problem. Actiontec makes a *decent* DSL
> >> gateway, but their routing software sucks. You would be best served by
> >> putting it in bridged mode and passing all traffic to a business class
> >> firewall appliance. Sonicwall, watchguard, etc make devices or the SMB
> >> market that all serve well and will protect your server substantially
> >> better
> >> than the built-in actiontec and not seize with multiple connections.
> >>
> >> -Cliff
> >>
> >>
> >> "Dane" <Dane@discussions.microsoft.com> wrote in message
> >> news:F3D1DA0D-FD16-4E73-800C-96EE23128DE9@microsoft.com...
> >> > Single NIC thru DSL router (Actiontec701) Static IP
> >> >
> >> > "Cliff Galiher" wrote:
> >> >
> >> >> How is it connected to the net?
> >> >>
> >> >> -Cliff
> >> >>
> >> >>
> >> >> "Dane" <Dane@discussions.microsoft.com> wrote in message
> >> >> news:2B1855F1-777C-425B-9DD5-0F4811CB6FC5@microsoft.com...
> >> >> > W2k3 (non R2) inst in 04, no recent hardware changes, only new sw is
> >> >> > updates,
> >> >> > single NIC
> >> >> >
> >> >> > Weird problem is that Exchange stops receiving/sending external mail
> >> >> > (services are still running fine so internal works) and external RDC
> >> >> > connections fail (internal connections still work fine)
> >> >> >
> >> >> > Running ICW fixes problem for a short time (20 to 40 minutes).
> >> >> > Exchange
> >> >> > sends and receives and a remote RDC can connect.
> >> >> >
> >> >> > If a RDC is made and left running, the amount of time before loss of
> >> >> > connection occurs can be extended for hours.
> >> >> >
> >> >> > In any case, browsing works all the time. Thanks in advance.
> >> >> >
> >> >> >
> >> >>
> >>
>

Merv
Thu May 15 15:23:18 PDT 2008

Great! Thanks for posting back with the fix Dane.

--
Merv Porter [SBS-MVP]
============================

"Dane" <Dane@discussions.microsoft.com> wrote in message
news:D425DB7B-A459-46C6-BBC7-ED5983262116@microsoft.com...
> Thanks to both. Ran the analyzer. It indicated a couple of obscure items.
> The
> one that seems to have fixed the issue was the recommendtion to create a
> registry entry to disable EDNS connection. Server has been running for
> almost
> 48 hours without connection problem for either rdc or email.
>
> "Cliff Galiher" wrote:
>
>> It doesn't increase the connection load. It is a single, stationary
>> connection that the actiontec stack prioritizes (because it is active.)
>> Without that active connection, nothing gets particularly prioritized, so
>> every syn/ack adds another one to the pile that the actiontec
>> (improperly)
>> tracks and eventually crashes its poor little OS. It is just a poor IP
>> stack that mismanages its own resources. The fact that, as you said, you
>> can continue to access internally, seems to indicate it is not SBS at
>> all,
>> but the router that quits getting traffic to the box.
>>
>> I understand the reluctance to throw money at the problem without proof,
>> so
>> if you have a spare consumer router around (linksys, netgear, etc) then
>> you
>> can even throw THAT on between the actiontec and SBS, still putting the
>> actiontec in gateway mode. See if that resolves the problem....
>>
>> -Cliff
>>
>>
>> "Dane" <Dane@discussions.microsoft.com> wrote in message
>> news:9D0E31F5-2A9A-4665-9D05-210ECEBC7679@microsoft.com...
>> > Thanks, but how does that address the fact that, if I force the
>> > addidional
>> > connection via and external RDC connection (increasing the connection
>> > "load")
>> > the connection is more reliable.
>> >
>> > "Cliff Galiher" wrote:
>> >
>> >> Yeah, that is probably your problem. Actiontec makes a *decent* DSL
>> >> gateway, but their routing software sucks. You would be best served
>> >> by
>> >> putting it in bridged mode and passing all traffic to a business class
>> >> firewall appliance. Sonicwall, watchguard, etc make devices or the
>> >> SMB
>> >> market that all serve well and will protect your server substantially
>> >> better
>> >> than the built-in actiontec and not seize with multiple connections.
>> >>
>> >> -Cliff
>> >>
>> >>
>> >> "Dane" <Dane@discussions.microsoft.com> wrote in message
>> >> news:F3D1DA0D-FD16-4E73-800C-96EE23128DE9@microsoft.com...
>> >> > Single NIC thru DSL router (Actiontec701) Static IP
>> >> >
>> >> > "Cliff Galiher" wrote:
>> >> >
>> >> >> How is it connected to the net?
>> >> >>
>> >> >> -Cliff
>> >> >>
>> >> >>
>> >> >> "Dane" <Dane@discussions.microsoft.com> wrote in message
>> >> >> news:2B1855F1-777C-425B-9DD5-0F4811CB6FC5@microsoft.com...
>> >> >> > W2k3 (non R2) inst in 04, no recent hardware changes, only new sw
>> >> >> > is
>> >> >> > updates,
>> >> >> > single NIC
>> >> >> >
>> >> >> > Weird problem is that Exchange stops receiving/sending external
>> >> >> > mail
>> >> >> > (services are still running fine so internal works) and external
>> >> >> > RDC
>> >> >> > connections fail (internal connections still work fine)
>> >> >> >
>> >> >> > Running ICW fixes problem for a short time (20 to 40 minutes).
>> >> >> > Exchange
>> >> >> > sends and receives and a remote RDC can connect.
>> >> >> >
>> >> >> > If a RDC is made and left running, the amount of time before loss
>> >> >> > of
>> >> >> > connection occurs can be extended for hours.
>> >> >> >
>> >> >> > In any case, browsing works all the time. Thanks in advance.
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>>