So, we have been having problems with getting thin clients to display a gdm login at remote sites.
Background:
Several years ago I upgraded our phone/data network. In the process our vendor specified a 1721 Cisco router at remote sites to connect to a 1841 at our main location. There are 3 remote locations connected via point to point clear channel T1 circuits.
The 1721 has a 10 mbs Ethernet connection, a 100 mbs Ethernet connection, and a serial connection for the T1. Data travels to the Main site via the 10mbs connection, and voice over IP interfaces with the local PBX via the 100 mbs port. While Troubleshooting a network upgrade at a remote site in March, I discovered that the 10 mbs connection had significant CRC errors. I found these errors on the switch and realized the Switch was set to auto negotiate and the router was coded to 10mbs Full-Duplex. The switch could not auto negotiate and then defaulted to half duplex. The immediate result was problemmatic connections (this consists of much jerky and hesitant responses) for our Telnet sessions to our ERP software. This was fixed by changing the managed switch port to 10mbs Full-duplex.
I then obtained some managed switches for my other two remote sites. Since I have made these changes I have alleviated the CRC errors and the jerky telnet sessions to our ERP software. PCAnywhere works much faster now as well.
The Problem:
At these other two remote sites I have a total of 4 thin clients. There are no thin clients at the first remote site. They have been working great for two years plus. Since the change only 1 will display a gdm login, and I am seeing duplicate ping responses. When I run wireshark at the Thin Client Server (Red Hat EL4) I see Duplicate packets often from the remote sites only. Also note that I have about 22 thin clients running, most are local. I am only experiencing this problem remotely.
When I ping to a local address everything appears normal.
Code:
# ping 192.168.2.170
PING 192.168.2.170 (192.168.2.170) 56(84) bytes of data.
64 bytes from 192.168.2.170: icmp_seq=0 ttl=64 time=0.134 ms
64 bytes from 192.168.2.170: icmp_seq=1 ttl=64 time=0.192 ms
64 bytes from 192.168.2.170: icmp_seq=2 ttl=64 time=0.221 ms
64 bytes from 192.168.2.170: icmp_seq=3 ttl=64 time=0.150 ms
64 bytes from 192.168.2.170: icmp_seq=4 ttl=64 time=0.226 ms
64 bytes from 192.168.2.170: icmp_seq=5 ttl=64 time=0.212 ms
64 bytes from 192.168.2.170: icmp_seq=6 ttl=64 time=0.115 ms
--- 192.168.2.170 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6000ms
rtt min/avg/max/mdev = 0.115/0.178/0.226/0.044 ms, pipe 2
When I ping a remote IP address I get a duplicate.
Code:
# ping 192.168.11.89
PING 192.168.11.89 (192.168.11.89) 56(84) bytes of data.
64 bytes from 192.168.11.89: icmp_seq=0 ttl=126 time=26.1 ms
64 bytes from 192.168.11.89: icmp_seq=0 ttl=126 time=26.1 ms (DUP!)
64 bytes from 192.168.11.89: icmp_seq=1 ttl=126 time=11.4 ms
64 bytes from 192.168.11.89: icmp_seq=1 ttl=126 time=11.4 ms (DUP!)
64 bytes from 192.168.11.89: icmp_seq=2 ttl=126 time=11.5 ms
64 bytes from 192.168.11.89: icmp_seq=2 ttl=126 time=11.5 ms (DUP!)
64 bytes from 192.168.11.89: icmp_seq=3 ttl=126 time=24.3 ms
64 bytes from 192.168.11.89: icmp_seq=3 ttl=126 time=24.3 ms (DUP!)
--- 192.168.11.89 ping statistics ---
4 packets transmitted, 4 received, +4 duplicates, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 11.454/18.378/26.149/6.917 ms, pipe 2
When I ping my gateway to the remote sites I get a duplicate.
Code:
# ping 192.168.2.200
PING 192.168.2.200 (192.168.2.200) 56(84) bytes of data.
64 bytes from 192.168.2.200: icmp_seq=0 ttl=255 time=0.737 ms
64 bytes from 192.168.2.200: icmp_seq=0 ttl=255 time=0.752 ms (DUP!)
64 bytes from 192.168.2.200: icmp_seq=1 ttl=255 time=0.488 ms
64 bytes from 192.168.2.200: icmp_seq=1 ttl=255 time=0.494 ms (DUP!)
64 bytes from 192.168.2.200: icmp_seq=2 ttl=255 time=0.541 ms
64 bytes from 192.168.2.200: icmp_seq=2 ttl=255 time=0.547 ms (DUP!)
64 bytes from 192.168.2.200: icmp_seq=3 ttl=255 time=0.577 ms
64 bytes from 192.168.2.200: icmp_seq=3 ttl=255 time=0.583 ms (DUP!)
--- 192.168.2.200 ping statistics ---
4 packets transmitted, 4 received, +4 duplicates, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 0.488/0.589/0.752/0.100 ms, pipe 2
When I ping remotely with a -R I fget this result:
Code:
# ping -R 192.168.11.89
PING 192.168.11.89 (192.168.11.89) 56(124) bytes of data.
64 bytes from 192.168.11.89: icmp_seq=0 ttl=126 time=19.8 ms
NOP
RR: 192.168.2.15
11.11.11.1
192.168.11.200
192.168.11.89
11.11.11.2
192.168.2.200
192.168.2.15
64 bytes from 192.168.11.89: icmp_seq=0 ttl=126 time=19.9 ms (DUP!)
NOP (same route)
64 bytes from 192.168.11.89: icmp_seq=1 ttl=126 time=19.2 ms
NOP (same route)
64 bytes from 192.168.11.89: icmp_seq=1 ttl=126 time=19.2 ms (DUP!)
NOP (same route)
64 bytes from 192.168.11.89: icmp_seq=2 ttl=126 time=26.2 ms
NOP (same route)
64 bytes from 192.168.11.89: icmp_seq=2 ttl=126 time=26.2 ms (DUP!)
NOP (same route)
--- 192.168.11.89 ping statistics ---
3 packets transmitted, 3 received, +3 duplicates, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 19.253/21.804/26.257/3.159 ms, pipe 2
What I have tried:
- Remove new network switch.
o No change.
- Swap ports of thin clients.
o No change. Working client does not move.
- Swap thin clients.
o Thin Client that was working doesn't. Non-working Thin Client now gets login. Is this a Magic Spot in the organization?
- Remove dhcpd.leases file. Restart dhcpd
o No Change.
- Clean out /tmp and /usr/tmp and /var/gdm on thin client server. Reboot.
o No change.
- Flush ARP tables on switches and routers. Restart Switches and Routers.
o No Change.
- Ship Thin Client to main site. Try out without making any config changes.
o Works great Here. In process of shipping back to remote site.
HELP ME!
