Please restrict access to regular users and above only! Guest accounts and twitted users shouldn't have access to DoorParty.

Here is the link for Rick Parrish's TelnetDoor: LINK As of Mystic 1.12a20, TelnetDoor is no longer needed, since Mystic has internal rlogin and telnet support.

Here is the link for plink, a command-line tool from the creators of PuTTy SSH: LINK

And now, for the instructions to set everything up to get you running!

1.) Extract the TelnetDoor archive to its own separate directory. I suggest something off the root directory, like C:\DOORPARTY

1. Move plink.exe to the same directory as TelnetDoor, something like C:\DOORPARTY.

2. Run MYSTIC.EXE -CFG in your Mystic directory and select Editors > Menu Editor, select the theme you want, then select the menu you plan on launching TelnetDoor.exe the Mystic internal rlogin from.

3. Add a menu item by typing / then I for Insert. Hit ENTER on the newly created menu item and change the Display Text, Lightbar Low, and Lightbar High to your taste (if you're not using lightbar menus for this selection, you can ignore those settings).

4. Change the Hot Key to whichever menu command you'd like, but make sure it's the same as the Display Text!

5. Set the required access level to your liking. I have mine set at s50 for security level 50, which is normal/validated user on my BBS.

6. Now hit your TAB key. This will let you add/edit menu commands. To get you up and running with the bare bones, select the default created command and hit ENTER.

7. Select Command and pick D3 (Exec DOOR32 program) IR (Outbound RLOGIN). Next, select Data and enter this:

c:\doorparty\doorparty.bat %3 %U


Change the [NEW] tag to your assigned BBS tag, and change RANDOM_CHARS to a random set of characters; the longer and more random, the better.

8. Now go to your DOORPARTY directory, create a new batch file named DOORPARTY.BAT and enter this into it:


set PORT=9999
set NODE=%1

start “SSH%1” /min plink -C -l USERNAME -pw PASSWORD -L -N timeout /t 1

telnetdoor.exe -R -Dc:\mystic\temp%1\door32.sys -S127.0.0.1 -P%PORT% -Y[NEW]%2

taskkill /fi “windowtitle eq SSH%1”


plink -C -l USERNAME -pw PASSWORD -P 2022 -L -N
timeout /t 2


Make sure you change the USERNAME and PASSWORD entries to your assigned username and password, and change the BBS tag of [NEW] to your assigned BBS tag.

When your application is approved, the [NEW] tag is going to be specific to your system and will be assigned uniquely to your BBS; this will identify your BBS to the DoorParty server. MAKE SURE TO CHANGE IT ONCE YOUR TAG IS ASSIGNED!

9. Either drop a link to the batch in your Startup folder, or create a task in Task Scheduler to launch that batch file on startup.

10. Select Access and assign an access level of at least regular user. Again, mine is s50.

Lastly, open up a command prompt and enter this before trying to connect to the server. THIS IS VERY IMPORTANT, you need to accept the host key to be entered into your registry this one time! It won't ask again after this. Just close the window after it connects. Remember to fill in your assigned username and password.

plink -l USERNAME -pw PASSWORD -P 2022 -L -N

That's it, you're done! Test it out by logging in and trying it out. If there's an issue connecting, double-check the instructions and your settings. If it all seems right, then either DoorParty is down, or more likely there might be other issues.

Check out the forums here to see if others have the same issue, or to ask for help.

sysop 07/17/2016 13:49