I have an unusual setup. Years ago (before there was 100Mbps Ethernet) my neighbor and I linked our houses using type 1 cable and 16Mbps Token Ring (TR). The distance limitation of Ethernet required us to go the TR route. Things were fairly simple, it was one flat network with a total of 20 TR attached devices in both houses. When fast Ethernet came out I upgraded the devices in my house and put a fast Ethernet card in my Novell server, two networks, things were still good. Cable modem sharing worked just okay because there were sporatic problems on the TR side due to NetWare 4.x not routing IP correctly. I solved this by letting Linux route IP between TR and Ether. My workstations on Ethernet were able to print to an all-in-1 printer/scanner/fax/copier down the street and they were able to print to my printers. We upgraded their side of the network when they got equipment with built in Ethernet adapters, plus put in a NetWare 4.x and Linux servers to route their fast Ether to TR. So we now had two fast Ethernets with a token ring in between. We both have cable modems and believe it or not sometimes they have problems with their modem when I don't have a problem, there are times when I have a problem and they dont. We have set up the workstations with primary and secondary default routes. Works fine. The other day the kid up the street got a new computer with XP on it. I installed the Novell client and he is able to log into my server (login script sits on screen for longer than normal but works, could be it's looking for a Win2000 or NT server as Novell is primary login?). This fast Ethernet connected XP machine is not able to see the workstation on Token Ring serving up the printer nor is it able to see my work group. Windows 95, 98 and Me all work fine. Anyone have any idea what's different about XP that it won't see the routed workgroups? This is posted to the Novell forum as there are two NetWare servers routing Ethernet <-> TR.