PDA

View Full Version : MQ Console not working



Draimen
01-24-2004, 10:35 PM
Can't get the MQ console to work, but I can't get a telnet session to work either. May need to post on the MQ site. I keep getting target computer actively refused the connection.

In my MQ.ini file I have:
[Telnet Server]
Enabled=0
LocalOnly=0
Port=6969
Welcome=MacroQuest telnet server
Password=

because if I not mistaken the mq2telnet plugin handles this now, so I have:
[Plugins]
mq2labels=mq2labels
mq2map=mq2map
mq2itemdisplay=mq2itemdisplay
mq2chatwnd=mq2chatwnd
mq2eqbugfix=mq2eqbugfix
mq2fps=mq2fps
mq2telnet=mq2telnet

In MQ2telnet.ini I have:
[Telnet Server]
; port = 0 off, else put the port number here
Port=6969
; localonly boolean -- supposedly does a get peer name to compare address
; but you must use the hostname not 127.0.0.1 or localhost when connecting
LocalOnly=0
Welcome=Successful login. Welcome to my undergroud lair.
LoginPrompt=login:
PasswordPrompt=password:

[Users]
;username=password
test=test

I try entering 127.0.0.1 6969 into the mq console, doesn't work. Have tried telnet from DOS prompt, doesn't work.

Any ideas?

Draimen
01-24-2004, 10:57 PM
OK, I can get telnet working fine. Still can't get the console to work on myseq. Do I need to use a certain port? How do I specify port, user, and pw? I have been trying 127.0.0.1 6969 in the start box but doesn't work.

Any help would be appreciated.

Draimen
01-24-2004, 11:01 PM
NM, I fixed it. Might help if I snoop around for the mqconsole.ini file thats right in front of me.

busby
01-25-2004, 11:22 AM
What is the MQ? I see it the tag under options but there is nothing under it nor is there any other information on it. Am I missing something?

MQSEQ2
01-25-2004, 01:35 PM
Nope, MQ = MacroQuest

Draimen
01-25-2004, 02:57 PM
MQ console working fine, but the user/pw in the ini isn't working. When i hit start it prompts me for login, the pw. The 1st time I type the login it always says invalid (although I am typing it right) but the 2nd time it works.

No biggie though.

MQSEQ2
01-25-2004, 03:37 PM
You can thank MQ2 for that, it's a known issue. Works fine with MQ1.