Thanks. That solved the problem.
I will turn this over to network support and let them figure out
where along the route the problem lies.

James Johnson                                 Email:  [EMAIL PROTECTED]
Systems Programmer                         Voice: 660-543-8065
Central Missouri State University       Fax:     660-543-8123
----- Original Message -----
From: "Post, Mark K" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 21, 2003 2:34 PM
Subject: Re: Routing question


> James,
>
> Sorry for the two replies, but I forgot one important point.  You should be
> able to turn off ECN via the /proc/sys/net/ipv4/tcp_ecn pseudo-file.  Most
> likely echoing a 0 into it will turn it off.  If you cat
> /proc/sys/net/ipv4/tcp_ecn, it will probably have a "1" in it right now.
>
> Mark Post
>
> -----Original Message-----
> From: James Johnson [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 21, 2003 3:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Routing question
>
>
> A traceroute to shows the following:
>
> listsrv:~ # traceroute www.nwmissouri.edu
> traceroute to info1.nwmissouri.edu (198.209.246.4), 30 hops max, 40 byte
> packets
>  1  core4-mfr.cmsu.edu (153.91.24.157)  51 ms  2 ms  1 ms
>  2  cmsufire-b.cmsu.edu (153.91.210.251)  1 ms  1 ms  1 ms
>  3  morenet-gw.cmsu.edu (153.91.251.254)  2 ms  2 ms  2 ms
>  4  kc-r10-01-atm3-0-3-102-aal5.mo.more.net (150.199.51.49)  33 ms  36 ms
> 37 ms
>  5  nwmsu-atm2-0-101-aal5.gw.more.net (150.199.50.174)  99 ms  42 ms  59 ms
>  6  info1.nwmissouri.edu (198.209.246.4)  482 ms !H  157 ms !H  71 ms !H
>
> The ouput from tcpdump has the following:
>  listsrv.cmsu.edu.1926 > info1.nwmissouri.edu.http: S [ECN-Echo,CWR]
>
> What does " S [ECN-Echo,CWR]" mean?
>
> James Johnson                                 Email:  [EMAIL PROTECTED]
> Systems Programmer                         Voice: 660-543-8065
> Central Missouri State University       Fax:     660-543-8123
> ----- Original Message -----
> From: "Eddie Chen" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, February 21, 2003 1:20 PM
> Subject: Re: Routing question
>
>
> >     You can do  a traceroute  on that IP address or tcpdump.   Most
> likely
> > a filter is set on the router or firewall.
> >
> >      "tcpdump  -i  ctc0 -w /home/echen/tcpdump.trace"   & --- run in
> > background
> >
> >      start you ftp /telnet
> >
> >     do   "ps"  and kill the process(tcpdump)
> >
> >       tcpdump -vvv -r /home/echen/tcpdump.trace  >
> > /home/echen/trace.listing
> >
> >      You should found   ICMP type 03 in the  trace and from  there it will
> > tell you which router
> >
> >
> >
> >                     James Johnson
> >                     <[EMAIL PROTECTED]        To:     [EMAIL PROTECTED]
> >                     msu.edu>               cc:
> >                     Sent by: Linux         Subject:     Routing question
> >                     on 390 Port
> >                     <[EMAIL PROTECTED]
> >                     arist.edu>
> >
> >
> >                     02/21/2003
> >                     06:18 PM
> >                     Please respond
> >                     to Linux on 390
> >                     Port
> >
> >
> >
> >
> >
> >
> > We have Linux machine running a listserv that is unable to reach
> > a specific ip address. I can not ftp telnet or e-mail to this address
> > from Linux. This address is external to our network. I can reach other
> > addresses that are external to our network from Linux.
> >
> > I can, however, reach this address from VM.
> >
> > Any thoughts as to why this is happening?
> >
> > We are running z/VM 4.2, SUSE 7.0 and using an OSA Express
> > Gigabit card.
> >
> > James Johnson                                 Email:
> [EMAIL PROTECTED]
> > Systems Programmer                         Voice: 660-543-8065
> > Central Missouri State University       Fax:     660-543-8123
> >
> >
> >
> >
> >
> > -----------------------------------------
> > This message and its attachments may contain  privileged and confidential
> information.  If you are not the intended recipient(s), you are prohibited
> from
> printing, forwarding, saving or copying this email.  If you have received
> this
> e-mail in error, please immediately notify the sender and delete this e-mail
> and
> its attachments from your computer.
> >
>

Reply via email to