Hi all: I have a very strange problem. I have a working LTSP 4.2 setup. Our network infrastructure is built around HP Procurve switches. We have our primary LTSP server in our machine room, and thin clients in two buildings throughout the building. All this works fine.
Then, one of our labs was rewired and a Netgear GSM7224 managed gigabit switch was installed. I took a working thin client from another space and plugged it into this new switch setup. It was able to PXE boot, but when the NFS root was mounted, it just scrolled "<nfs_server_ip> Not responding, still trying...". If I unplug the thin client from the netgear and plug it into a drop from the HP switch, it works fine. I can usually wait until GDM shows up, then move it back, and it will continue to work until the thin client gets rebooted. I have tested: 1) Wyse thin client on netgear, server in machine room; 2) Old PC PXEboot on netgear, server in machine room. 3) Old PC connected to "dumb switch" plugged into netgear, server in machine room. 4) Old PC connected to negear, test server also on netgear All these fail. Interestingly enough, old PC on HP switch with server on netgear works. We have many workstations on the netgear switch, all of wich are NFS mounting without issue. It only seems to be LTSP 4.2 that has a problem. We can't upgrade to LTSP5, as the change in model forces us to violate one of our core requirements: RHEL/CentOS base (required for apps we're running). Any suggestions? I have no idea what to start tweaking on the netgear... --Jim ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
