Telnet troubles

Samefudge · Post by **Samefudge** » Tue Mar 25, 2003 10:47 am

Using SRC-20030308 compiled, the first time I ran MQ and logged in, I could telnet in from my Linux box and it worked (I opened the telnet session during world load, after hitting LOAD from char select). After that EQ session, I had to ALT-F4 to because my mouse locked up. From then on, after that successful session, I only get refused connections, and nothing else has changed about my setup.

I've tried using different source builds, all give the same result, even going back to 20030308. And yes, I can ping the EQ box just fine, and have rebooted and power cycled both boxes. I know the Linux box can see the EQ box fine, because GPS works in SEQ.

Any ideas on what happened?

eqjoe · Post by **eqjoe** » Tue Mar 25, 2003 12:13 pm

In your MQ directory you have a good MacroQuest.ini file, and in that file you have under the [Telnet Server] header, Enabled=1 and Port=23(or whatever you want to use for a port)

Samefudge · Post by **Samefudge** » Tue Mar 25, 2003 12:52 pm

file is fine, Telnet settings are the same as they were when the session first worked... but now it diesn't work, using the same .ini file.

eqjoe · Post by **eqjoe** » Wed Mar 26, 2003 2:05 pm

Telnet will not work until after the DLL is loaded. Are you using the standard telnet port?

I tested this and found that I got a connect but no prompt. I suspect it has something to do with my custom build as I have removed most all modified response. This does not bother me because I dont use Telnet.

Does the spewfile give you any hints as to what is going on?

Mckorr · Post by **Mckorr** » Wed Mar 26, 2003 3:46 pm

I always wondered if you needed the Telnet service enabled on WinNT/2k/XP to use this feature of MQ... a lot of folks disable that service for security reasons....

Samefudge · Post by **Samefudge** » Fri Mar 28, 2003 11:02 am

But see that's the thing.... it worked fine until I crashed and now it won't connect even after a re-compile of the same source, cold boot both machines, etc. It's very odd behaviour.

Revenge · Post by **Revenge** » Fri Mar 28, 2003 11:20 am

I was recently writing a perl based server from which I could obtain a data report. When I telnet in from linux, I can type out a line, then press Enter, and the whole line is sent (like block mode?)

I connected to the same server from a WinXP shell, however each time I pressed a key, the data was sent to the server right away.

When I connect to MacroQuest duirng play, it asks me for my password, I type 1 character and it says wrong password and boots me out.

Clearly someone has borked the MQ code. May I suggest, that you dont accept the data until a linefeed is detected, and THEN process the incoming line?

L124RD · Post by **L124RD** » Fri Mar 28, 2003 12:13 pm

Salutations,
So are you saying that you Are connecting through the winXP shell to the MQ telnet server? I don't understand that either. I downloaded puTTY, connected through it to the macroquest shell, it works fine.

Revenge · Post by **Revenge** » Mon Mar 31, 2003 7:36 pm

Salutations,
So are you saying that you Are connecting through the winXP shell to the MQ telnet server? I don't understand that either. I downloaded puTTY, connected through it to the macroquest shell, it works fine.

It sounds like the easy solution would be to simply not use winXP's built in telnet program and just go get puTTY instead, however it would be nice to not have to worry about that.

Mckorr · Post by **Mckorr** » Tue Apr 01, 2003 8:49 am

Build in Telnet in any version of Windows is fairly limited. I'd always suggest downloading a different Telnet client, if only for ease of use. There are a number of decent freeware clients available.

Telnet troubles

Telnet troubles

macroquest.ini ...

Telnet hell

puTTY vs Telnet