Hey, thanks for all the quick responses! On 9 Sep 2004 at 14:37, dpk wrote: > A few questions to aide in debugging. > What static route makes it work? 35.8.232.0 mask 255.255.255.0 35.8.232.1 > What does tracert output from a client show? Nothing. It can't even make one hop to the server without timing out. > What subnet mask and gateway do you use on the Netware server? mask=255.255.255.0 GW=35.8.232.1 > Are the server and clients on the same physical network segment? Uh... I don't know. They're in the same building; clients over in your building don't have the problem (see below). > netstat -r from both the server and clients may also be helpful. SERVER: Destination Gateway Flags Metric Netif Age 35. 8.232. 0 wkar.msu.edu US 1 Q57_1_EII_EII 1148844 Default com3-rtr-s232.net GUS 1 Q57_1_EII_EII 10552 CLIENT: ========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 35.10.42.1 35.10.42.111 1 35.8.0.0 255.248.0.0 35.10.42.111 35.10.42.111 1 35.10.42.111 255.255.255.255 127.0.0.1 127.0.0.1 1 35.255.255.255 255.255.255.255 35.10.42.111 35.10.42.111 1 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 224.0.0.0 224.0.0.0 35.10.42.111 35.10.42.111 1 255.255.255.255 255.255.255.255 35.10.42.111 35.10.42.111 1 Default Gateway: 35.10.42.1 ========================================================================== And On 9 Sep 2004 at 15:30, Surato, Michael wrote: > There are a couple of things to try. First attempt to run a traceroute > (tracert 35.8.232.2) from the client to the server. This will tell you > where the problem is from the client end. The next thing to test is a > trace from the server to the client (nwtrace 35.10.x.x). One of these > traces should give the address/name of the offending router. As I said above, client times out on the first hop. From the server to the client, the first (and only) hop is to 35.8.188.1 (huh? what router is that?); the rest of the hops time out. > The other issue to check is to make sure that the default route on the > server points to 35.8.2.3. This particular router seems to work better > than other routers in the configuration here. ? 35.8.232.3 is not a router. Default route points to 35.8.232.1 Finally, On 9 Sep 2004 at 14:57, John Resotko wrote: > On the Netware side of things, you will need to advertise Netware > services on the TCP/IP protocol by configuring SLP, and designating one > of your Netware servers as the primary SLP DA (directory agent) server. Thank you. I may well not have configured this properly, and will check out the Novell TIDs you suggested. However, I'm not sure that SLP is the problem per se, since I have some clients in another building/network segment who can log in and do stuff on the server using pure IP, and I didn't do anything special to make that work. Many thanks again. Kim Geiger Information Technologist MSU Broadcasting Services 538 Communication Arts & Sciences Building East Lansing, MI 48824 - 1212 517-432-9527 x 429