>What I don't understand is why a line error would effect a direct dial >in on the Lan to a server on the LAN.I would think that the TCP/IP link >to the out-side world ( T-1) would have no bearing other than the DNS/IP >server that is done via the State.Does anyone has a clue ?
What the heck is a "Direct dial in on the lan???"
Is it a LAN connection or is it a dial-up connection? I would suspect it to be treated as a LAN connection by TF server, though it is limited to the performance of the Terminal server dialups. If the outbound connection (to the internet) is flooding the internal network with bad packet traffic then it could be responsible for the poor performance all the way around. This would also depend upon the need for services such as routing and naming by each TCP/IP host... If the hosts on your LAN have to wait for good data from a name server or router, and this router is getting hit with bad traffic, then it will slow everything down. I have seen this lots of times at work, especially from poorly configured routers and switches that re-broadcast crap that they should not.
>> >Thanx for everybody's time and yes Dan I can see the reason for a modem >ON the server now ;-0
The ability to directly access the TF-Server CPU would help you isolate this problem to other networked assests, (rather than being continuously victimized by them) and possibly provide connecting clients some relief from its effects. --- Daniel O'Leary, Sysop KloneZone Mac - A TeleFinder 5.7 Mac/Windows BBS 532 Verna Trail North, Fort Forth TX USA 76108 (817)367-2558 (Voice) (817)367-2712 (Dial-in) 1:130/1015 (Fido) klonezone.tfnet.org (TFNet) kz.eaze.net (Internet) http://kz.eaze.net (WWW)
