Re: Win2K running on INS -- MIDRANGE-L

from the MS TCP/IP Services manual:
can you ping your own loopback 12.0.0.1 ? This verifies your
ip config of the local interface.
Ping your own address. This verifies the binding between the protocol
and the adapter card.
If the above 2 don't work-either not set right (or dare I say it -
corrupted)
Have you seen if ICMP echo been disabled (either on your w2000 or
on the other network machines. This means don't respond to ping or
other ech requests/replies. Not sure where u set this in W2K.
jim

----- Original Message -----
From: "Art Tostaine, Jr." <art@link400.com>
To: <MIDRANGE-L@midrange.com>
Sent: Thursday, May 17, 2001 10:17 PM
Subject: RE: Win2K running on INS


> Following is results of the ping, then the tracert.  I wonder if this is
> some kind of Windows 2000 server IP security thing?
>
> C:\DOCUME~1\ADMINI~1>ping 192.168.3.4
>
> Pinging 192.168.3.4 with 32 bytes of data:
>
> Destination host unreachable.
> Destination host unreachable.
> Destination host unreachable.
> Destination host unreachable.
>
> Ping statistics for 192.168.3.4:
>     Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 0ms, Maximum =  0ms, Average =  0ms
>
> C:\DOCUME~1\ADMINI~1>tracert 192.168.3.4
>
> Tracing route to 192.168.3.4 over a maximum of 30 hops
>
>   1  Destination host unreachable.
>
> Trace complete.
>
> Thanks!
>
> Art Tostaine, Jr.
> CCA, Inc.
> Jackson, NJ 08527
>
> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Walden H. Leverich
> Sent: Thursday, May 17, 2001 10:14 AM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: Win2K running on INS
>
>
> Who is reporting the destination unreachable? Can you also do a "tracert
> 192.168.3.4" and post the results.
>
> -Walden
>
> -----Original Message-----
> From: Art Tostaine, Jr. [mailto:art@link400.com]
> Sent: Wednesday, May 16, 2001 8:17 PM
> To: MIDRANGE-L@midrange.com
> Subject: RE: Win2K running on INS
>
>
> I have config'd the network adapter as 192.168.3.6, subnet 255.255.255.0,
> and gateway 192.168.3.4
>
> Art Tostaine, Jr.
> CCA, Inc.
> Jackson, NJ 08527
>
> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of Jeffrey Silberberg
> Sent: Wednesday, May 16, 2001 7:22 PM
> To: MIDRANGE-L@midrange.com
> Subject: Re: Win2K running on INS
>
>
>
>     Do a "netstat -rn"  from a command window and send it back along with
> the address and
> submask you have in use...
>
> Jeffrey M. Silberberg
> Independent Consultant
> CompuDesigns, Inc.
> (770) 399-9464
>
> AS SOON AS I KNOW THE ANSWERS
> THEY CHANGE THE QUESTIONS
>
> ----- Original Message -----
> From: Art Tostaine, Jr. <art@link400.com>
> To: <MIDRANGE-L@midrange.com>
> Sent: Wednesday, May 16, 2001 4:52 PM
> Subject: Win2K running on INS
>
>
> > I have Win2k Server running on my 270's INS.  I have two ethernet ports,
> but
> > only one connected to the network.
> >
> > I can see others on the network from the Win2k console, but I can't ping
> > them.  I get destination host unreachable, even though they are on the
> same
> > subnet.
> >
> > The clients can't ping the Win2k box, but they can see it in network
> > neighborhood.  I have TCP/IP setup properly on the Win2k box.
> >
> > The midrange-l question, then, is, is there anything special about this
> > installation that would cause Win2k to not respond to pings, or
otherwise
> > not be a normal W2k server?
> >
> >
> >
> > Art Tostaine, Jr.
> > CCA, Inc.
> > Jackson, NJ 08527
> >
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> david@midrange.com
> > +---
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---