Force Telnet
Moderator: Mod Squad
Force Telnet
Is their a way to force telnet out to a single ip addy with no other options? WG 2.0 DOS flavour.
Yep, when you create your telnet module page, put in the command line box:
O ###.###.###.### 23 B
The letter O means Open a connection, #'s are the IP address (I assume you can use simple addresses as well), 23 is the port number, B = Binary connection.
If you want, you can also add the option #BBSNAME so it shows the destination when someone does a user list instead of just showing you being in Telnet client.
I'm assuming you're using the Vircom TCP/IP package.
O ###.###.###.### 23 B
The letter O means Open a connection, #'s are the IP address (I assume you can use simple addresses as well), 23 is the port number, B = Binary connection.
If you want, you can also add the option #BBSNAME so it shows the destination when someone does a user list instead of just showing you being in Telnet client.
I'm assuming you're using the Vircom TCP/IP package.
It's been a while since I used this, but I believe that message means the host is refusing the connection for some reason. What are you trying to connect to? Is it another server within your network or somewhere else? If it is yours, you may have to define (in the host server software) what addresses are permitted to connect to it, or what port/protocol to allow connections on. For example, the server could be listening for rlogin connections on 513 and you're trying to telnet to 23.
Its a mud server, I can connect to it localhost or via term program such as putty on what ever port I set the mud to connect on. Testers have been able to connect to it no problems (on the port I specify) but testing it with WG i get that error and can't connect...its running on a different server then WG.
Ok, so using Putty, you are connecting via telnet with no problem. Check your WG menu and make sure all the command line settings match the Putty settings. Have you tried using Putty from the computer you're using for WG to make sure there is connectivity from there? Have you tried using the WG telnet and just entering the address when it asks, rather than trying to set up the menu? That would tell us if you're problem is with your settings or something else. Are you able to set up a WG telnet connection to connect with anything else? Is it a public server that I could test from my BBS? If I can get it to work for mine, I can send you the actual command line (you can PM me an address if you don't want to post it). I assume you have a static IP that your testers are connecting to, and you are using your internal network IP (192.168.*.*) to connect to it, right?
Sorry so many questions. Just lots of possiblities still
Sorry so many questions. Just lots of possiblities still
Are you using Vircom's Major TCP/IP Package or Galacticomm's ICO Package?
This is the way to setup the Channel Groups using Major TCP/IP for WG2 DOS.
Set your Incoming Telnet channels
Incoming Telnet channels are the means by which people on the internet will be able to login to your BBS remotely. Each incoming telnet channel uses up one license off of your galacticomm six-packs. You may need to purchase sufficient numbers of six-packs depending on the maximum number of concurrent incoming telnet users you would prefer. If you do not wish to setup an incoming Telnet channel, you should at least put up one channel for testing purposes while your system is in the configuration phase by using the license of one of your modems.
Use the following procedure to add a Telnet channel group:
· From the main configuration menu (CNF), select F1 - Hardware configuration
· At this point, you should be editing the BBSMAJOR.MSG parameters.
· Use the down arrow key to get to next available channel group.
· Press F2 - Pick one
· From the Channel Group Type window, select TELNET
· Starting channel number should be the next one available (per the last channel group)
· Number of channels as desired, as long as you don’t run out of six-pack licenses.
· Once done, press on F10 Save and Exit to go back to the main configuration menu.
Set your Telnet/Rlogin dial-out channels
Telnet/RLogin dial-out channels are used to disguise Telnet/RLogin sessions to look like a normal Modem connection, allowing your BBS to connect to other services via the internet, saving you hundreds of dollars in long-distance or X.25 costs. Specifically, you can use them to
run various connectivity add-ons that weren’t designed to work with MajorTCP/IP. (Worldlink, Chatlink, Interlink, Maillink, Entertainment Teleconference Link-up, Galacticomm's Dial-out module). Each dial-out channel uses up a license out of your Galacticomm six-packs.
Use the following procedure to add a Telnet/RLogin Dial-Out channel group:
· From the main configuration menu (CNF), select F1 - Hardware configuration
· At this point, you should be editing the BBSMAJOR.MSG parameters.
· Use the down arrow key to get to next available channel group.
· Press F2 - Pick one
· From the Channel group type window, select MODEM
· Starting channel number should be the next one available (per the last channel group)
· Number of channels as desired, as long as you don’t run out of six-pack licenses.
· I/O base adress ...............................should be skipped (down arrow)
· Maximum baud rate ........................ skip
· Lock port at this baud rate .............. skip
· Echo keystrokes to this channel ...... skip
· Hardware type, you should press F5 for TELOUT
· Offset between channels ................ skip
· Init String should be left as is or you could replace it with ATZ
· Once done, press on F10 Save and Exit to go back to the main configuration menu
When a third party module requires you to enter a channel and dialing string to use, you can tell it to use one of the dialout channels and this dialing string: ATDT<numeric IP adress>[:port][R]
Example: ATDT199.84.216.1 (Connect to default port 23 in telnet mode)
ATDT199.84.216.1:2500 (Connect to port 2500 in telnet mode)
ATDT199.84.216.1R (Connect to default port 23 in RLogin mode)
ATDT199.84.216.1:2500R (Connect to port 2500 in Rlogin mode)
This is the way to setup the Channel Groups using Major TCP/IP for WG2 DOS.
Set your Incoming Telnet channels
Incoming Telnet channels are the means by which people on the internet will be able to login to your BBS remotely. Each incoming telnet channel uses up one license off of your galacticomm six-packs. You may need to purchase sufficient numbers of six-packs depending on the maximum number of concurrent incoming telnet users you would prefer. If you do not wish to setup an incoming Telnet channel, you should at least put up one channel for testing purposes while your system is in the configuration phase by using the license of one of your modems.
Use the following procedure to add a Telnet channel group:
· From the main configuration menu (CNF), select F1 - Hardware configuration
· At this point, you should be editing the BBSMAJOR.MSG parameters.
· Use the down arrow key to get to next available channel group.
· Press F2 - Pick one
· From the Channel Group Type window, select TELNET
· Starting channel number should be the next one available (per the last channel group)
· Number of channels as desired, as long as you don’t run out of six-pack licenses.
· Once done, press on F10 Save and Exit to go back to the main configuration menu.
Set your Telnet/Rlogin dial-out channels
Telnet/RLogin dial-out channels are used to disguise Telnet/RLogin sessions to look like a normal Modem connection, allowing your BBS to connect to other services via the internet, saving you hundreds of dollars in long-distance or X.25 costs. Specifically, you can use them to
run various connectivity add-ons that weren’t designed to work with MajorTCP/IP. (Worldlink, Chatlink, Interlink, Maillink, Entertainment Teleconference Link-up, Galacticomm's Dial-out module). Each dial-out channel uses up a license out of your Galacticomm six-packs.
Use the following procedure to add a Telnet/RLogin Dial-Out channel group:
· From the main configuration menu (CNF), select F1 - Hardware configuration
· At this point, you should be editing the BBSMAJOR.MSG parameters.
· Use the down arrow key to get to next available channel group.
· Press F2 - Pick one
· From the Channel group type window, select MODEM
· Starting channel number should be the next one available (per the last channel group)
· Number of channels as desired, as long as you don’t run out of six-pack licenses.
· I/O base adress ...............................should be skipped (down arrow)
· Maximum baud rate ........................ skip
· Lock port at this baud rate .............. skip
· Echo keystrokes to this channel ...... skip
· Hardware type, you should press F5 for TELOUT
· Offset between channels ................ skip
· Init String should be left as is or you could replace it with ATZ
· Once done, press on F10 Save and Exit to go back to the main configuration menu
When a third party module requires you to enter a channel and dialing string to use, you can tell it to use one of the dialout channels and this dialing string: ATDT<numeric IP adress>[:port][R]
Example: ATDT199.84.216.1 (Connect to default port 23 in telnet mode)
ATDT199.84.216.1:2500 (Connect to port 2500 in telnet mode)
ATDT199.84.216.1R (Connect to default port 23 in RLogin mode)
ATDT199.84.216.1:2500R (Connect to port 2500 in Rlogin mode)
I will have to try loading it on the same server as WG and try localhost.