[THIN] Re: Wireshark analysis for pay

From my limited understanding (I have only been here for 2 days):

The vendor plugged a cable into some device that is to be used for DR 
replication in the future
Device was properly configured at the time the cable was plugged in
SAN had not been implemented yet
So it appears the new cable was trying to replicate all network traffic to an 
unconfigured device that had no storage on the other side
The network was flooded with retries and waits and timeouts etc etc etc ad 
naseum

The phone system went wack and they thought it was a problem with the phone 
system.  They replaced the server a processor and who knows what else.  The 
also replaced the switch the phone system was connected too.

According to our fellow list member (and since verified by a couple of others 
who have responded) the Wyse Xenith thin clients are extremely sensitive to all 
this crap going on in the network.  Once the cable was unplugged and firewall 
changes reversed, there have been ZERO reports of the connection reset by peer.

If there is any other info, I will have to have our fellow list member give 
non-customer specific details.

Thanks



Carl Webster

Consultant and Citrix Technology Professional

http://www.CarlWebster.com<http://www.carlwebster.com/>

________________________________
From: thin-bounce@xxxxxxxxxxxxx [thin-bounce@xxxxxxxxxxxxx] on behalf of Scott 
Hahn [scott.hahn@xxxxxxxxx]
Sent: Tuesday, October 18, 2011 10:45 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Wireshark analysis for pay

Carl-
Great to hear you have resolution.  Without damning the guilty can you give us 
some guidance on the change that caused this? The rest of us with Wyse based 
customers could probably benefit.

Scott

On Oct 18, 2011, at 11:36 AM, Webster wrote:

This issue appears to have been resolved with the help of a fellow Thin List 
member.

The Wyse Xenith device is extremely sensitive to network traffic and noise.  A 
change had been made by the soon-to-be previous IT services provider.  THey had 
insisted their change couldn't be affecting anything.  WRONG!  As soon as their 
change was undone, bingo, no more ICA connection reset by peer issues.  ZERO. :)

Needless to say this customer is very happy, their users are happy and our 
fellow list member has turned me into the hero of the day.  I am now this IT 
departments new bestest friend ever.  Pays to know or have access to really 
smart people.

Thanks


Carl Webster
Consultant and Citrix Technology Professional
http://www.CarlWebster.com<http://www.carlwebster.com/>
________________________________
From: thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx> 
[thin-bounce@xxxxxxxxxxxxx<mailto:thin-bounce@xxxxxxxxxxxxx>] on behalf of 
Webster [webster@xxxxxxxxxxxxxxx<mailto:webster@xxxxxxxxxxxxxxx>]
Sent: Monday, October 17, 2011 4:38 PM
To: thin@xxxxxxxxxxxxx<mailto:thin@xxxxxxxxxxxxx>
Subject: [THIN] Wireshark analysis for pay

Have a customer with Wyse zero client devices.  They are constantly getting 
"ICA Connection Reset by Peer".  According to Google, this issue seems to occur 
only with Wyse thin clients.  This customer has a Wyse maintenance contract but 
Wyse appears to not be concerned with fixing this issue for this customer on 
their devices.

Customer has followed Wyse's instructions and obtained Wireshark traces on 
three devices having this connection issue.  Since Wyse appears to not care to 
resolve the issue, the customer has asked me to see if I can find someone who 
could analyze the Wireshark traces (for pay) and see if they could possibly 
find what the culprit may be.  The users are having this connection reset issue 
continually and as you can image the users and the IT staff would like this 
resolved promptly.

If you are experienced at reading Wireshark traces and would like to make some 
money while doing so, contact me off list. 
webster@xxxxxxxxxxxxxxx<mailto:webster@xxxxxxxxxxxxxxx>

Thanks

Carl Webster
Consultant and Citrix Technology Professional
http://www.CarlWebster.com<http://www.carlwebster.com/>

Other related posts: