tony@scotty.dccs.upenn.edu (Anthony Olejnik) (06/20/89)
I'm having a problem with IBM's PCLAN program. The problem appears with both versions 1.2 and 1.3 (I don't know about earlier versions). I've noticed that when using either Ungermann-Bass PCNIUs (with Release 16.0 of their TCP/PC software) or WD8003E's (with PC/TCP v2.03 pl 1 software) the PCLAN server does not drop non-existent sessions. Both of the HW/SW combinations are using the NetBIOS as referenced in RFC's 1001 & 1002. Clients who connect to the server are still "seen" by the server even after the PC is turned off. This presents a problem the next day when the same clients attempt to connect to the server again. If the server has available NETBIOS/TCP sessions, then the client is able to re-connect. However, this still leaves a non-existent session on the server end. If the server does not have any available NETBIOS/TCP sessions, then the client is not able to re-connect. Is this a problem with PCLAN? Is this a problem with my configuration of PCLAN? (I start the server via the following command: net start srv test /cac:0) Is this a problem with both UB and FTP's software? Is this a (RFC 1001/2) NetBIOS bug? Any help would be greatly appreciated. Thanks. --tony olejnik University of Pennsylvania Data Communications and Computing Services Suite 221A 3401 Walnut Street Philadelphia, PA 19104 (215) 898-9408 tony@dccs.upenn.edu
gts@violet.berkeley.edu (Greg Small) (06/24/89)
= Article 26 of comp.protocols.pcnet: Date: 19 Jun 89 21:16:56 GMT = From: tony@scotty.dccs.upenn.edu (Anthony Olejnik) = = I'm having a problem with IBM's PCLAN program. When using either Ungermann- = Bass PCNIUs (with Release 16.0 of TCPPC) or WD8003E's (with PC/TCP v2.03 pl = 1) the PCLAN server does not drop non-existent sessions. = = Clients who connect to the server are still "seen" by the server even after = the PC is turned off. This presents a problem the next day when the same = clients attempt to connect to the server again. If the server has available = NETBIOS/TCP sessions, then the client is able to re-connect. However, this = still leaves a non-existent session on the server end. The temporary solution for UB TCP-PC 16.0 is to turn on TCP Heartbeats. This allows the server to time-out the connection. RFC1001/1002 also provides a separate heartbeat for Netbios sessions only but that is not implemented in 16.0 (comming in 16.1?). You should check PC/TCP for a similar option. There is a similar problem that PC Net/LAN does not clean up a Netbios connection if the workstation IP address is changed while the server has a Netbios connection open. When the workstation logs back into the server the connection under the old IP address is maintained. I guess from your question that the UB TCPPC 16.0 and the PC/TCP interoperate OK under RFC1001/1002? Gregory T Small (415)642-5979 Personal Computer Networking & Communications gts@violet.Berkeley.EDU Workstation Support Services - Software Group ucbvax!jade!gts 267 Evans Hall SPGGTS@UCBCMSA.BITNET University of California, Berkeley, Ca 94720