Hi, I am unable to access my clients running v7.6.13 via telnet/raw socket connection.
I can connect, and I get the welcome screen, but any command after that closes the connection.
This does not occur on v7.5.x clients. Downgrading these clients to v7.5.1 fixes the problem, which seems to me like this is a problem with v7.6.x.
Connecting via localhost gives the same result.
Is this happening to anyone else?
Telnet connection closes after entering command
Moderators: Site Moderators, FAHC Science Team
-
PantherX
- Site Moderator
- Posts: 7020
- Joined: Wed Dec 23, 2009 9:33 am
- Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB
Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400 - Location: Land Of The Long White Cloud
- Contact:
Re: Telnet connection closes after entering command
Welcome to the F@H Forum WatsOnTV,
Can you please provide more details like:
1) What is the destination client settings?
2) What commands are you entering?
AFAIK, there haven't been any issues with telnet in the latest stable release.
Can you please provide more details like:
1) What is the destination client settings?
2) What commands are you entering?
AFAIK, there haven't been any issues with telnet in the latest stable release.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Re: Telnet connection closes after entering command
Hi, from further investigation, I can see that the client has clearly been updated to close the connection if the user is not authenticated and the command is not "auth <password>". This seems like an odd change, but that's ok, I'll deal. Thanks for your help.