Connection problems with Wyse 3200LE terminals

cuttressb · ‎02-12-2003

We are having intermittent problems when connection to 3548 switches using DHCP with our Wyse terminals. Sometimes they work fine and other times they cannot find the Server. We have set the port and the terminal to different speeds and duplex's without any success. The switch port also has portfast enabled so the port should start to forward ASAP.

Any ideas???

7rbowenii · ‎02-12-2003

C- I have had some problems with Cisco switches and WYSE terminals. Almost everyone of them has been resolved by setting both the terminal and the switchport to full/100. The WYSE terminals we use aren't real happy with any other settings. Even half/100 or 10/full don't work real well. Make sure that you are manually setting your speed and duplex on both ends.

Let me know if this helps..

-Bo

cuttressb · ‎02-12-2003

We have a cluster with 4 servers and it seems like we had a problem with DHCP hanging on one of the served address's. The terminal would not connect when it grabbed a certain DHCP address and even after the terminal was disconnected from the network you could still ping the address by ip or name(MAC address) . Strange. We took the one IP address out of the pool and we seem to be OK now. I have tried forcing the speed and duplex and your right it does normaly help but not in this case.

Thanks for your help

7rbowenii · ‎02-12-2003

C-

It sounds like you may have an IP or MAC duplication in your network. What is reponding to the ip address after you take your terminal off? What is the mac? Compare that mac with the one for the terminal.

-bo

cuttressb · ‎02-14-2003

I'm thinking it was the cluster that was repling back after the terminal was disconnected from the network. The MAC address was the MAC of the terminal. Everything is working OK again and the ip address stopped responding after about an hour. Is it possible the cluster had it and would not release it? It seemed when we tried to connect with the Wyse if it picked that IP up again it would not connect but if it picked up a DHCP address from another DHCP Server it would connect.

Thanks

7rbowenii · ‎02-14-2003

You almost have to have an IP conflict somewhere. Espeacially if a different address returned different results. A WYSE terminal is not going to act differently due to the ip address assigned by a DHCP server. Also, the cluster most certainly should not respond to an ip address that doesn't exist. What port are you seeing the mac address of the ip (SH ip arp)? What is connected to that port? I believe you need to look into this further. Also, are you connecting to a remote site? Using IP SPoofing? This could have an effect, but I am bit that well versed on IP spoofing, perhaps someone else can shed some light on that if you are using it. Let me know what you find out, if you don't research the problem now, it will most likely come back to haunt you in the future.

-Bo