Windows Forum

Ask something
Discussion Locked

3com vs netgear

0 helpful
2 replies

by dgates_1 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We run Windows TSE 4.0 and Citrix Metaframe 1.8 with WYSE terminals (2300se). THe connection works with a terminal-3comhub-network. However, if we try to go from terminal - netgearhub - network, the connection is dropped when the terminal tries tocommunicate with the dhcp server. If I enable DNS and add the host and IP of the dns server ( also the dhcp server) on the network configuration option on the terminal setup, it works. WHY?

2 replies

by buzzwang

You'd have to check netgear's site for the technical specifics, but it sounds like that netgear hub either isn't properly running n-way or simply doesn't pass the packets properly for a dns request. I find this somewhat surprising, but perhaps that's because it's a hub? I've used netgear switches (the small, cheapo ones) at home and at work without issue. Is it an old hub? 10/100? Full-duplex? If it's an older model, or looks as though it's seen better days, I'd purchase a new one, prefferably a switch instead of a hub.

by dgates_1

It is a 10/100 hub and although I said it works with DNS enabled on the terminal, it doesn't work all of the time. We have since purchased a 3com hub and the same thing happens. These are both new hubs. The terminal works fine with the old 3com hub. I am thinking that it has something to do with the connection. We have PC's connecting at 100MBps but the terminals connect only at 10 (WYSE 2300). These old terminals seem to work with the old hub but not the newer ones. Its very strange that it works sometimes, sometimes it doesn't and that there is a connection light until the connection is attempted to the terminal server at which point it drops the connection.
What is n-way?

This discussion is closed to new replies.