[THIN] Re: Latency issues from Down Under?
- From: Jennifer Hooper <jennifer.hooper@xxxxxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Fri, 3 Dec 2004 12:47:58 -0800
Would that do any good, since she's not even able to connect to the server?
Thanks,
Jennifer
-----Original Message-----
From: msemon@xxxxxxx [mailto:msemon@xxxxxxx]
Sent: Friday, December 03, 2004 11:48 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Latency issues from Down Under?
Speed Screen Latency Reduction?
Original Message:
-----------------
From: Jennifer Hooper jennifer.hooper@xxxxxxxxxxxxx
Date: Fri, 3 Dec 2004 11:19:18 -0800
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Latency issues from Down Under?
Thanks Will... I didn't think it should. Network is telling me everything
is fine within the VPN side of things, so I wonder if it's not something
outside. This is becoming a rather critical issue for us, so I'm going to
press back on them.
In the meantime, is there anything that I can check on the Citrix server to
help get her connected? This is NT4, TSE, running Metaframe 1.0. Old old
old stuff.
Thanks,
Jennifer
_____
From: William Treloar [mailto:treloarw@xxxxxxxxxxxxx]
Sent: Tuesday, November 30, 2004 3:19 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Latency issues from Down Under?
No, there is something wrong, check all your hops could be a stuffed Switch,
router, VPN concentrator.
get it all checked out. shouldn't be getting delays like this. Check for
saturation also.
-----Original Message-----
From: Jennifer Hooper [mailto:jennifer.hooper@xxxxxxxxxxxxx]
Sent: Wednesday, 1 December 2004 11:28 a.m.
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Latency issues from Down Under?
Hi Gang -
So I have a problem with some users in Asia/Pacific area. A couple of
weeks ago, everything was fine. But lately, the user has been getting
cannot connect to Citrix Server, Can't find the application and other neat
Citrix errors when she cannot run her Siebel pubapplication. We had some
WebICA issues last week after it was moved to a new web server, but that was
all resolved by including *.ica as an approved MIME type. Now, everything
works fine, except from the Sydney office.
The Sydney office is an 'e-suite', utilizing their network connection to
VPN to our VPN concentrator here in the US. From there, there is a setup of
3 Metaframe 1.0 servers on NT4, located in the same datacenter as the
concentrator. I had her do some ping tests, and here's what the results
look like:
Pinging domain controller [xx.x.x.xxx] with 32 bytes of data:
Reply from xx.x.x.xxx: bytes=32 time=191ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=181ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=190ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=721ms TTL=126
Request timed out.
Request timed out.
Request timed out.
Reply from xx.x.x.xxx: bytes=32 time=171ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=181ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=170ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=571ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=170ms TTL=126
Ping statistics for xx.x.x.xxx:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 721ms, Average = 193ms
Pinging server1 [xx.x.x.xx] with 32 bytes of data:
Reply from xx.x.x.xx: bytes=32 time=170ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=191ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=170ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=1082ms TTL=126
Request timed out.
Reply from xx.x.x.xx: bytes=32 time=331ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=181ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=321ms TTL=126
Reply from xx.x.x.xx: bytes=32 time=550ms TTL=126
Request timed out.
Request timed out.
Ping statistics for xx.x.x.xx:
Packets: Sent = 30, Received = 27, Lost = 3 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 1082ms, Average = 213ms
Pinging server2 [xx.x.x.xxx] with 32 bytes of data:
Reply from xx.x.x.xxx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=181ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=190ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=170ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=190ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=1002ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=471ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=932ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=240ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=180ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=170ms TTL=126
Reply from xx.x.x.xxx: bytes=32 time=782ms TTL=126
Request timed out.
Reply from xx.x.x.xxx: bytes=32 time=420ms TTL=126
Ping statistics for xx.x.x.xxx:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 1002ms, Average = 265ms
Tracing route to server1 [xx.x.x.xx]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 400 ms 341 ms 180 ms server1 [xx.x.x.xx]
Trace complete.
So my question is, is this indicative of the latency issues that you see
from remote offices, and is there anything I can do to help improve the
situation?
Thanks so much!
Jennifer
Jennifer Hooper
Peregrine Systems, Inc.
Sr. Network Engineer
mailto:jennifer.hooper@xxxxxxxxxxxxx <mailto:jennifer.hooper@xxxxxxxxxxxxx>
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
********************************************************
This Weeks Sponsor Activaeon.com
Reduce licensing costs with activAeon XA and
get one month completely free.
http://www.activaeon.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
********************************************************
This Weeks Sponsor Activaeon.com
Reduce licensing costs with activAeon XA and
get one month completely free.
http://www.activaeon.com
**********************************************************
Useful Thin Client Computing Links are available at:
http://thin.net/links.cfm
ThinWiki community
http://www.thinwiki.com
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thin.net/citrixlist.cfm
Other related posts:
