Re: Very weird ping problem

From: William Stacey [MVP] (staceyw_at_mvps.org)
Date: 09/24/05 

Date: Sat, 24 Sep 2005 08:57:23 -0400

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.
>

Relevant Pages

  • RE: cannot connect computer
    ... if I type in the url of the server i get through ok. ... client computer to SBS domain. ... | I am unable to ping the sbs server by ip or name. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... That means that SBS has a static *private* IP on your LAN. ... Not being able to ping "the server" is probably not a sign of a problem...and is also technically inaccurate. ... I understand the desire to keep your server minimalist and only run exchange, but DNS and DHCP should be considered "essential" SBS components. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... It is held by SBS. ... There is no router in between the ISP's connection and the SBS server. ... So in essence, the WAN port will not ping, but it does get out on the internet, and OWA will work through it. ... That would be a very odd configuration considering what 'appears' to be the rest of your network layout. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... public IP is assigned to the external NIC of SBS. ... Is it installed with a standard install of SBS Server? ... I think I posted a question somewhere on the forums that I would have gladly ONLY installed Exchange if I could. ... So in essence, the WAN port will not ping, but it does get out on the internet, and OWA will work through it. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... The truth is that ping packets are a basic troubleshooting tool and a router *shouldn't* be monkeying with them. ... And changing a packet intended to to troubleshoot a connectivity issue defeauts the purpose of sending the packet in the first place...as the destination suddenly becomes ambiguous. ... The ISP configured the original device and the device actually PROPERLY recreates NAT ping packets and passes them to the servers, but the SBS server was not part of that initial configuration. ...
    (microsoft.public.windows.server.sbs)