Very weird ping problem

TheMSsForum.com: The Microsoft Software Forum

I have a few networks here.
EXT FW&WAP -> SBS2003 w/ ISA2004 -> Internal LAN
-> LAN GW&WAP -> Internal LAN
DSL -> 192.168.1.x -> 192.168.16.x
SBS is 192.168.1.200
LAN GW&WAP is 192.168.1.2
EXT FW&WAP is 192.168.1.1

SBS Internal is 192.168.16.4
LAN GW&WAP is 192.168.16.1

LAN/DHCP (on SBS) Default Gateway is 192.168.16.1
SBS Defautl GW in on Ext NIC and is 192.168.1.1
No GW defined on SBS internal NIC

Problem....
Everytime I try to ping or tracert from my SBS Server to the internet
my External Network Interface goes offline and reports "unplugged"
and I get a "Hardware Error" in my CMD windows. A few minutes later
the interface re-initializes and goes online.

This server publishes content to the internet frequently every day,
and serves as a Web, FTP, SMTP and other services server, all day
long. Nothing else causes this, it only happens if I try to Ping or
Tracert.

Any ideas? It's a home server, that
is very much not critical, and merely there for my ability to learn about
things and keep in touch with other avenues of the industry while not
managing my corporate network at the office.

In addition to that, everything else works. It is serving web/ftp/smtp
requests all day long, without error. So... it is my preference not to just
"fix" a problem by removing hardware and registry settings for something
like this that is of rare concern to me. I'd rather try to identify
with the support of others, cause clearly I have reached my threshold here,
the root cause of the situation to which I am experiencing.

I would be honored if anyone would be kind enough to humor my idealism in
this
situation, and would furthermore be thrilled to actually identify something,
whether resolution/root cause is ever found or not.
Top

Re: Very weird ping problem by William

William
Sat Sep 24 07:57:23 CDT 2005

I am guessing because ICMP (ping) packets are normally blocked by
firewall/network software, because they can be used for denial of service
attacks and misc deeds. I am guessing that the server tcp stack sees the
ping reply and disables the stack temporarily. If that is the case, that
would be an error in the implementation, instead of just ignoring the ICMP
packets. I have never heard about this kind of behavior in XP or Windows
200X, so maybe it is a SBS thing. Potentially, I guess it could be some
driver issue as well. If you had another SBS box, I guess you could prove
this out.

--
William Stacey [MVP]

"MCSEGURU" <mcseguruhere@aol.com> wrote in message
news:OArlWDKwFHA.596@TK2MSFTNGP12.phx.gbl...
>I have a few networks here.
> EXT FW&WAP -> SBS2003 w/ ISA2004 -> Internal LAN
> -> LAN GW&WAP -> Internal LAN
> DSL -> 192.168.1.x -> 192.168.16.x
> SBS is 192.168.1.200
> LAN GW&WAP is 192.168.1.2
> EXT FW&WAP is 192.168.1.1
>
> SBS Internal is 192.168.16.4
> LAN GW&WAP is 192.168.16.1
>
> LAN/DHCP (on SBS) Default Gateway is 192.168.16.1
> SBS Defautl GW in on Ext NIC and is 192.168.1.1
> No GW defined on SBS internal NIC
>
> Problem....
> Everytime I try to ping or tracert from my SBS Server to the internet
> my External Network Interface goes offline and reports "unplugged"
> and I get a "Hardware Error" in my CMD windows. A few minutes later
> the interface re-initializes and goes online.
>
> This server publishes content to the internet frequently every day,
> and serves as a Web, FTP, SMTP and other services server, all day
> long. Nothing else causes this, it only happens if I try to Ping or
> Tracert.
>
> Any ideas? It's a home server, that
> is very much not critical, and merely there for my ability to learn about
> things and keep in touch with other avenues of the industry while not
> managing my corporate network at the office.
>
> In addition to that, everything else works. It is serving web/ftp/smtp
> requests all day long, without error. So... it is my preference not to
> just
> "fix" a problem by removing hardware and registry settings for something
> like this that is of rare concern to me. I'd rather try to identify
> with the support of others, cause clearly I have reached my threshold
> here,
> the root cause of the situation to which I am experiencing.
>
> I would be honored if anyone would be kind enough to humor my idealism in
> this
> situation, and would furthermore be thrilled to actually identify
> something,
> whether resolution/root cause is ever found or not.
>


Top

Re: Very weird ping problem by Steven

Steven
Sat Sep 24 09:49:10 CDT 2005

I have never experienced that myself but would I would do is to try a
different network [different brand] adapter to see if it still happens. If
it does not it probably is a quirk with the nic or drivers. If it still
happens in would appear to by operating system related. I have had good luck
with Intel Pro 100+ pci and they are very cheap used on Ebay. SysInternals
makes a free program called Tdimon that you could use to monitor tcp/ip
while you attempt to ping to see what happens. It will not tell you
explicitly what is wrong but give you an idea of what is going on. --- Steve


http://www.sysinternals.com/Utilities/TdiMon.html --- Tdimon


"MCSEGURU" <mcseguruhere@aol.com> wrote in message
news:OArlWDKwFHA.596@TK2MSFTNGP12.phx.gbl...
>I have a few networks here.
> EXT FW&WAP -> SBS2003 w/ ISA2004 -> Internal LAN
> -> LAN GW&WAP -> Internal LAN
> DSL -> 192.168.1.x -> 192.168.16.x
> SBS is 192.168.1.200
> LAN GW&WAP is 192.168.1.2
> EXT FW&WAP is 192.168.1.1
>
> SBS Internal is 192.168.16.4
> LAN GW&WAP is 192.168.16.1
>
> LAN/DHCP (on SBS) Default Gateway is 192.168.16.1
> SBS Defautl GW in on Ext NIC and is 192.168.1.1
> No GW defined on SBS internal NIC
>
> Problem....
> Everytime I try to ping or tracert from my SBS Server to the internet
> my External Network Interface goes offline and reports "unplugged"
> and I get a "Hardware Error" in my CMD windows. A few minutes later
> the interface re-initializes and goes online.
>
> This server publishes content to the internet frequently every day,
> and serves as a Web, FTP, SMTP and other services server, all day
> long. Nothing else causes this, it only happens if I try to Ping or
> Tracert.
>
> Any ideas? It's a home server, that
> is very much not critical, and merely there for my ability to learn about
> things and keep in touch with other avenues of the industry while not
> managing my corporate network at the office.
>
> In addition to that, everything else works. It is serving web/ftp/smtp
> requests all day long, without error. So... it is my preference not to
> just
> "fix" a problem by removing hardware and registry settings for something
> like this that is of rare concern to me. I'd rather try to identify
> with the support of others, cause clearly I have reached my threshold
> here,
> the root cause of the situation to which I am experiencing.
>
> I would be honored if anyone would be kind enough to humor my idealism in
> this
> situation, and would furthermore be thrilled to actually identify
> something,
> whether resolution/root cause is ever found or not.
>


Top