Ours is slow too but not that I notice big problems. I remember the
70's and TSO response times of minutes.
Ping statistics :
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 226ms, Maximum = 261ms, Average = 237ms
>
On Fri, Nov 6, 2009 at 5:08 AM, Scott <sc...@aitrus.org> wrote:
> I'd suggest running a traceroute to the location, through the day. If it's
> not a DoS then it's probably the telephone companies playing politics with
> each other.
>
> Scott
>
> On Thu, Nov 5, 2009 at 7:14 AM, William Janulin
> <william.janu...@aspg.com>wrote:
>
>> I am experiencing similar problems here is the U.S.
>>
>> Bill Janulin
>> Mgr Tech Support & Product Dev.
>> ASPG, Inc.
>>
>>
>>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
>> Behalf Of Jim McAlpine
>> Sent: Thursday, November 05, 2009 10:13 AM
>> To: IBM-MAIN@bama.ua.edu
>> Subject: IBM Remote Development System
>>
>> We are having awful response time problems to our RDP system from here
>> in
>> the UK. The system was fine this morning but it seems that the problem
>> occurs at around 08.30 through 09.30 am Dallas time on most days. It is
>> sometimes taking over a minute to get a response from a TSO session even
>> when out guest system is doing nothing. We also can't get a connection
>> via
>> the client vpn connection as it just times out. Ping to our guest
>> system
>> results in the following during these periods -
>>
>> Reply from 172.29.127.162: bytes=32 time=234ms TTL=58
>> Request timed out.
>> Reply from 172.29.127.162: bytes=32 time=233ms TTL=58
>> Reply from 172.29.127.162: bytes=32 time=215ms TTL=58
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Reply from 172.29.127.162: bytes=32 time=220ms TTL=58
>> Reply from 172.29.127.162: bytes=32 time=237ms TTL=58
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Reply from 172.29.127.162: bytes=32 time=253ms TTL=58
>> Reply from 172.29.127.162: bytes=32 time=202ms TTL=58
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Reply from 172.29.127.162: bytes=32 time=204ms TTL=58
>> Reply from 172.29.127.162: bytes=32 time=204ms TTL=58
>> Request timed out.
>>
>> Are any other users in the UK getting similar problems ?
>>
>> Jim McAlpine
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
>> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
>> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
--
Wayne V. Bickerdike
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
