Real Time Ascend Maling List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) mail attachment problem
Hi ,
Just to add another point,
Check with your Telco whether your customer calls transitted a couple of
COs before hit your MAX 4000 ...
The transmission quality between COs is another concerns .. we experienced
same problems a couple months back and later we found out that the one of
the CO partial lost synch with others CO that caused this problems ...
Good luck ...
At 23:15 10-05-99 -0500, Jerry O'Brien wrote:
>> 1) Just to confirm it is the MTU size, could u try dial into the failing
>> max and then ping your ISP network with large packet ( packet size >
>1600
>> ) and then use a smaller packet as well ( packet size < 1400 ) ..
>
>Well, that's interesting. I'm not sure what this means, but I can't ping
>with anything close to 1500 bytes. It bogs down around 150, and completely
>hangs at 165. If I go to the "good" Max and ping back to the "bad" one, I
>get the same result, but I can ping the mail server from the "good" Max
>using any size packet. I'm wondering if the 56K line's MTU is
>misconfigured...The Cisco is set to 1500. I can't see the CSU's though, as
>I'm off-site.
>
>Should I be able to ping with any size packet in this configuration?
>
>> 2) Have you check your failing MAX MRU size ? ...
>> If you are using the MAX 4000 , then check it under Ethernet--> Answer
>> ---> PPP --> MRU
>> set it to 1500 as well ..
>
>Yes, it was set to 1500.
>
>>
>> 3) Is your T1 line connected to your upstream provider terminated in your
>> Cisco Router ?
>
>No. We're going out of the 2nd Max's serial interface.
>
>Jerry
>
>
>----- Original Message -----
>From: KY Lee <kylee@tm.net.my>
>To: Jerry O'Brien <jobrien@cuttingedge.net>; <ascend-users@bungi.com>
>Sent: Monday, May 10, 1999 8:56 PM
>Subject: Re: (ASCEND) mail attachment problem
>
>
>> HI Jerry ,
>>
>>
>> IMHO, it looks like it is the MTU misconfiguation problems .
>> I have a few points here , might be you want to try those
>>
>> 1) Just to confirm it is the MTU size, could u try dial into the failing
>> max and then ping your ISP network with large packet ( packet size >
>1600
>> ) and then use a smaller packet as well ( packet size < 1400 ) ..
>>
>> 2) Have you check your failing MAX MRU size ? ...
>> If you are using the MAX 4000 , then check it under Ethernet--> Answer
>> ---> PPP --> MRU
>> set it to 1500 as well ..
>>
>> 3) Is your T1 line connected to your upstream provider terminated in your
>> Cisco Router ? If yes, Is the encapsulation PPP or HDLC ? Otherwise can u
>> use enable CDP neighbor to check what equipment your ISP used ? It your
>ISP
>> is using CISCO equipment , then that will be most likely reason that you
>> don't encounter any problems
>>
>>
>> Cheers
>>
>>
>>
>> At 09:03 10-05-99 -0500, Jerry O'Brien wrote:
>> >We have a pair of Adtran 56/64 DSU/CSU terminating the 65K line. Both are
>> >set to 1500 MTU. I'm not sure about upstream provider's equipment, but
>from
>> >the failing Max we're going over the 56K line, through a Cisco 2501
>router,
>> >over the LAN to the 2nd Max (the one that users can send the attachment
>> >through), and then out the serial line through a T1 CSU and out to the
>> >upstream. It seems to me the connection to our upstream provider must be
>OK,
>> >since the 2nd Max works.
>> >
>> >The Cisco MTU is set to 1500 (see below) and the errors look reasonably
>low.
>> >
>> >Jerry
>> >
>> >Serial0 is up, line protocol is up
>> > Hardware is HD64570
>> > Internet address is 192.168.1.1/30
>> > MTU 1500 bytes, BW 56 Kbit, DLY 20000 usec, rely 255/255, load 22/255
>> > Encapsulation PPP, loopback not set, keepalive set (10 sec)
>> > LCP Open
>> > Listen: cdp
>> > Open: ipcp
>> > Last input 00:00:00, output 00:00:00, output hang never
>> > Last clearing of "show interface" counters never
>> > Queueing strategy: fifo
>> > Output queue 0/40, 15594 drops; input queue 0/75, 0 drops
>> > 5 minute input rate 1000 bits/sec, 2 packets/sec
>> > 5 minute output rate 5000 bits/sec, 2 packets/sec
>> > 4846542 packets input, 410033079 bytes, 0 no buffer
>> > Received 2 broadcasts, 0 runts, 0 giants
>> > 1704 input errors, 1704 CRC, 0 frame, 0 overrun, 0 ignored, 1619
>abort
>> > 5324957 packets output, 2416421820 bytes, 0 underruns
>> > 0 output errors, 0 collisions, 57 interface resets
>> > 0 output buffer failures, 0 output buffers swapped out
>> > 45283 carrier transitions
>> > DCD=up DSR=up DTR=up RTS=up CTS=up
>> >----- Original Message -----
>> >From: KY Lee <kylee@tm.net.my>
>> >To: Jerry O'Brien <jobrien@cuttingedge.net>; ## Dusty Carden
>> ><dusty@netease.net>; <ascend-users@bungi.com>
>> >Sent: Saturday, May 08, 1999 11:56 PM
>> >Subject: Re: (ASCEND) mail attachment problem
>> >
>> >
>> >> Hi ,
>> >>
>> >> This could be the MTU size misconfiguration for the PPP. I wonder what
>> >> equipment do you use to connect to your upstream service Provider and
>also
>> >> terminating equipment used by your service provider?. Besides that what
>> >> type of equipment are u connecting your 56K leased line to the LAN.. ?
>> >More
>> >> details will enable me to rule out whether it is MTU/MRU problems. ..
>> >> Cheerios .
>> >>
>> >> At 09:05 06-05-99 -0500, Jerry O'Brien wrote:
>> >> >Thanks Dusty,
>> >> >
>> >> >Most of the folks who are having trouble here are using very recent
>Win98
>> >> >boxes, so I doubt whether their DUN or winsock are old. I forgot to
>> >mention
>> >> >I am running 6.1.7 on both maxen. The one that works sits on our
>central
>> >LAN
>> >> >and connects via T1 to our upstream provider. The failing unit
>connects
>> >to
>> >> >the LAN via 56K leased line. No other problems with the failing unit,
>> >just
>> >> >this attachment thing.
>> >> >
>> >> >Jerry
>> >> >
>> >> >
>> >> >----- Original Message -----
>> >> >From: ## Dusty Carden <dusty@netease.net>
>> >> >To: Jerry O'Brien <jobrien@cuttingedge.net>
>> >> >Sent: Thursday, May 06, 1999 8:06 AM
>> >> >Subject: Re: (ASCEND) mail attachment problem
>> >> >
>> >> >
>> >> >> I had this with a couple of WIN95 clients. Upgrading their winsock
>> >> >> and dial up networking fixed it. This was through a MAX 6. They
>could
>> >> >> dial in to the 4004 in the same rack and have no problems. Both
>boxes
>> >> >> are running 6.1.7. I was surprised that upgrading their winsock
>fixed
>> >the
>> >> >> problem and I am still not sure what the deal was.
>> >> >>
>> >> >> Dusty
>> >> >>
>> >> >> ----- Original Message -----
>> >> >> From: Jerry O'Brien <jobrien@cuttingedge.net>
>> >> >> To: <ascend-users@bungi.com>
>> >> >> Sent: Wednesday, May 05, 1999 11:23 PM
>> >> >> Subject: (ASCEND) mail attachment problem
>> >> >>
>> >> >>
>> >> >> Hi,
>> >> >>
>> >> >> I'm out of ideas here...
>> >> >>
>> >> >> I have a group of users who can't send email attachments through one
>of
>> >my
>> >> >> Max 4048s. Another identical box at a different site works fine, so
>I'm
>> >> >> ruling out customer equipment and DNS. Anyone know of anything in
>the
>> >4K
>> >> >> configuration that could cause this? It happens to files as small as
>> >40K,
>> >> >so
>> >> >> I don't think it's a size problem. My mail log (Linux, sendmail 8.?)
>> >says
>> >> >> the server is waiting to receive mail data, but then times out after
>> >two
>> >> >> hours. I think the clients are giving up and closing sooner, but the
>> >mail
>> >> >> server always waits for the timeout.
>> >> >>
>> >> >> TIA
>> >> >>
>> >> >> Jerry O'Brien
>> >> >>
>> >> >>
>> >> >> ++ Ascend Users Mailing List ++
>> >> >> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
>> >> >> To get FAQ'd: <http://www.nealis.net/ascend/faq>
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> >++ Ascend Users Mailing List ++
>> >> >To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
>> >> >To get FAQ'd: <http://www.nealis.net/ascend/faq>
>> >> >
>> >>
>> >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> >> KY Lee
>> >> Network Development Engineer, !networX
>> >> !nternet Services, COINS
>> >> TELEKOM MALAYSIA BERHAD [128740-P]
>> >> Fax : +60 -(0)3 - 7042204
>> >> http://www.tm.net.my
>> >>
>> >> Time Zone : GMT+ 8
>> >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> >>
>> >>
>> >
>> >
>> >++ Ascend Users Mailing List ++
>> >To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
>> >To get FAQ'd: <http://www.nealis.net/ascend/faq>
>> >
>>
>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> KY Lee
>> Network Development Engineer, !networX
>> !nternet Services, COINS
>> TELEKOM MALAYSIA BERHAD [128740-P]
>> Fax : +60 -(0)3 - 7042204
>> http://www.tm.net.my
>>
>> Time Zone : GMT+ 8
>> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>> ++ Ascend Users Mailing List ++
>> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
>> To get FAQ'd: <http://www.nealis.net/ascend/faq>
>>
>>
>
>
>++ Ascend Users Mailing List ++
>To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
KY Lee
Network Development Engineer, !networX
!nternet Services, COINS
TELEKOM MALAYSIA BERHAD [128740-P]
Fax : +60 -(0)3 - 7042204
http://www.tm.net.my
Time Zone : GMT+ 8
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>