>>How come the TF can not disconnect it if the users has >>reached the idle time? Otherwise, users can not re-log in >>after the connection is lost for some ISP problem? > > >>try to disconnect the users to allow them to re-connect to >>the server. But the connection window is saying something >>like "Stopping the node......." It keep it on the screen >>and I can not really disconnect the users to save them. >
TO RUSTY:::::
I hope the following data will be helpful....
---------------------------------
User using powerPC 7100/80 --or-- SuperMac C600/180 User using Mac OS 8.0 --or-- Mac OS 8.1 User Using TF Mac User verson 5.7 (PowerPC) User Using US Rob 36K --or-- global teleport 28K modem User Using apple OT version 1.2 --or-- v1.3 User Using Apple TCP/IP version 1.2 --or-- v1.3 User using PPP OT v1.2/ OT/PPP v1.0.1 --or-- v1.01
Server using PowerPC 7100/66 AV Server using Mac OS 8.0 Server using Mac OS v Server verson 5.7 server using apple OT version 1.2 server using apple TCP/IP version 1.2
Conditions present: ..........
1) I have noticed the same, or similar problem using TCP/IP with dedicated 56K leased line to ISP.
2) A client connects to the BBS via internet TCP/IP using TF User Modem Ops through their own dial-up ISP.
3) user Starts a data transfer.
4) The (server???) ISP can not keep up with the data transfer.
5) server and client get many re-transmits and duplicate data packs (detected by IP Net Monitor), then the server stops sending/receiving data because (I am guessing) that the TF User re-transmit command or continue command packits are not being received by TF Server or are received in the incorrect order???; or they are being lost by one of the ISPs (server???).
6) Otherwise, all LAN TCP/IP TF User Client operations (so far) appear to work perfectly. It is only when data transfers occur between different ISPs via the internet that this problem occurs.
............
Analysis and corrective action:... ------------------------------
At that time the problem occurs, TF server appears to be connected, but there is no communication (no TCP/IP activity as monitored by IP NetMonitor) between the client ISP and the server ISP. The client has to force quit TF user; the TF Server operator must do a stop node hard and then restart that node.
I use a dedicated 56K leased line via a portmaster router to the internet.
clients can connect via my LAN, or via TCP/IP over the internet using my 10T Hub/8 Ethernet connection to my TF server.
