[c-nsp] Cisco equipment and Wyse Rapport/Thin Clients - Might be abit off topic

[Zahrt, Frank]

Use Ethereal to sniff the server and see if it is getting the request
and compare it to the request that the Thin Client has sent? Granted,
this will take a couple Ethereal setups, but it is a good way to find
the break.

If it is receiving it, then it's probably not the network.

If it's not, well then you have something to fix with the switches,
although port filtering at layer 2 does not seem to be part of the setup
you have.


HTH,
Frank

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Craig Gauss
Sent: Thursday, December 01, 2005 10:39 AM
To: cisco-nsp at puck.nether.net
Cc: thin at freelists.org
Subject: [c-nsp] Cisco equipment and Wyse Rapport/Thin Clients - Might
be abit off topic

We are having a heck of a problem getting our Rapport server to talk to
the thin clients on our network.  Wyse support keeps wanting to place
the blame on the network.  I figured I would post a question here and
see if anyone has any ideas.
 
Our current setup is something like this:
 
 
Cisco 4507R Core Switch -----> MS Windows 2003 Server (DHCP, DNS, WINS)
VLAN 100
  |
  |
Cisco 3550 Switch VLAN 10 ----> MS Windows 2003 Server (Rapport) VLAN 10
- Static IP
  |
  |
Cisco 3550 Switch VLAN 10
  |
  |
Cisco 3550 Switch VLAN 10 ---> Wyse Thin Client VLAN 10 - DHCP IP
 
 
The Thin Client gets a DHCP address no problem.  When it comes to
getting anything from the Rapport Server is where the problems come in.
The Thin Client can be rebooted and polled from the Rapport server but
when trying to push or pull an image nothing really goes through.  The
Thin Client will reboot when an image is pushed or pulled, but it never
finds the image on the server.  From what we gathered with Wyse, using
Ethereal, that the thin client is sending the request to the server, but
nothing is coming back.
 
They are thinking something in our network is blocking it.  We have no
access lists or anything on the switches that I could see would be
"blocking" the 4011 port.  Of course they have no ideas for us as of
things to check or configuration changes that need to be changed
 
Any ideas on this?
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/