Any ideas why I can telnet to the world within Synchronet but not to my internal network ?
I'm trying to setup a telnet into another system on my *internal* network an not getting anywhere.
I have added an entry for this system and the command line is duped from the other telnet entries, I just modified the hostname to reflect what I have in \windows\hosts file. I have even tried just using the IP address.
It just hangs.....
I can telnet to the system in question from my SBBS system with a regular telnet program, both to the hostname and to the IP.
Any ideas why I can telnet to the world within Synchronet but not to my internal network ?
Any ideas why I can telnet to the world within Synchronet but not to my internal network ?
You have not really given us a lot of information on the physical topology o the network. You have an internal network and internet connectivity, and an SBBS box, but how are they hooked together?
Can you ping the system in question? Does it actually have a telnet daemon running? Do you have a multi-homed box functioning as a gateway? Is there firewalling going on? Maybe you need to put an entry in your routing table(
Tell me more and I will try to help.
It just hangs.....
You mean it never returns an error message? You have to close down SBBSCTRL?
Any ideas why I can telnet to the world within Synchronet but not to my internal network ?
It might be the interface you have the telnet server bound to (outbound teln connections use the same interface) can not reach this other machine. If you have multiple network interfaces (cards) in your computer, then may need to change your bound Interface in SBBSCTRL->Telnet->Configure to "<ANY>".
It just hangs.....
You mean it never returns an error message? You have to close down SBBSCT
No errors. It says 'Press Ctrl-]for a control menu anytime'. Then it says '[Hit a key]'
I hit a key......
it says 'Connecting to: myopia'
and then nothing happens. I can hit Ctrl-] and tell it to disconnect and ge back to the BBS.
I already have the Interface IP bound to <ANY>, but maybe I'll bind it to my NIC and see happens.
Any ideas why I can telnet to the world within Synchronet but not to m internal network ?
It might be the interface you have the telnet server bound to (outbound t connections use the same interface) can not reach this other machine. If have multiple network interfaces (cards) in your computer, then may need change your bound Interface in SBBSCTRL->Telnet->Configure to "<ANY>".
Already configured like that.
Here's the error I get in the log file AFTER I hit Ctrl-D to disconnect from the hung telnet attempt:
9/12 09:03:24p Node 1 Ran external: Myopia
9/12 09:03:26p Node 1 Telnet gate to myopia.ujoint.org port 23 on socket 404
9/12 09:03:42p !TELGATE ERROR 10038 sending on socket 404
9/12 09:03:42p !ERROR 10038 closing socket 404
9/12 09:03:42p Node 1 Telnet gate to myopia.ujoint.org finished
Again, I can telnet to myopia from this machine just fine, but not via Synchronet.. ?
Any ideas why I can telnet to the world within Synchronet but not to my internal network ?
9/12 09:03:24p Node 1 Ran external: Myopia
9/12 09:03:26p Node 1 Telnet gate to myopia.ujoint.org port 23 on soc 404
9/12 09:03:42p !TELGATE ERROR 10038 sending on socket 404
9/12 09:03:42p !ERROR 10038 closing socket 404
9/12 09:03:42p Node 1 Telnet gate to myopia.ujoint.org finished
This error simply means you aborted the connection attempt. Try being patien and waiting for the real connection failure message.
Any ideas why I can telnet to the world within Synchronet but not to my internal network ?
Do you have tcp/ip networking setup and IP numbers assigned on you lan?
9/12 09:03:42p !TELGATE ERROR 10038 sending on socket 404
9/12 09:03:42p !ERROR 10038 closing socket 404
9/12 09:03:42p Node 1 Telnet gate to myopia.ujoint.org finished
This error simply means you aborted the connection attempt. Try being pat and waiting for the real connection failure message.
OK, got my unix machine back up and running and started trying all this stuf again.
Still don't work. I let it sit for 133 minutes ( I went shopping ) and I st got no error, it just sat there.
I have a LinkSys broadband router that links my internal network to the outs world. My internal network is 192.168.1. I have connectivity between my BBS machine (internal network 192.168.1.100 or delta.ujoint.org) and my unix computer (internal network 192.168.1.50 or myopia.ujoint.org). I tested my connectivity by using ping, ftp, and telnet. These all work fine from either machine to either machine.
Try running '*telgate myopia.ujoint.org' causes you to just hang there with connection. running '*telgate delta.ujoint.org' works. Now I am really confusinededed...ded.
This behavior is identical if I am telneted into my BBS from inside my netwo or from an outside (other side of my router) host.
my 'hosts' file( same on both my systems ):
192.168.1.100 delta delta.ujoint.org
192.168.1.50 myopia myopia.ujoint.org
Since I do networking support as part of my real job, this is one of those things that I am determined to figure out why it doesn't work, and I am stumped. I don;t know what's ahppening inside of the baja code for 'telnet_gate', but that's the only place I can figure this is going wrong...
I have only one NIC on both systems, the IP's are static, SBBS has been boun to <ANY> and is now bound to 192.168.1.100 and all results are the same.
Help?
I have a LinkSys broadband router that links my internal network to the outs world. My internal network is 192.168.1. I have connectivity between my BBS machine (internal network 192.168.1.100 or delta.ujoint.org) and my unix computer (internal network 192.168.1.50 or myopia.ujoint.org). I tested my connectivity by using ping, ftp, and telnet. These all work fine from either machine to either machine.
Try running '*telgate myopia.ujoint.org' causes you to just hang there with connection. running '*telgate delta.ujoint.org' works. Now I am really confusinededed...ded.
I really don't have a clue as to why it isn't working. The telnet_gate funct simply opens a socket, binds it, and attempts a connect to the address (and port) specified. Nothing complex. Here is the actual code:
I really don't have a clue as to why it isn't working. The telnet_gate funct simply opens a socket, binds it, and attempts a connect to the address (and port) specified. Nothing complex. Here is the actual code:
I've found the source of my problem, and the problem is the negotiations tha take place between a telnet server and a telnet client before a login prompt displayed. When using telnet_gate to connect to a telnetd or RFC telnet server, the telnet server attempts to do negotiations with the client to establish some things before a login propmpt gets thrown out. Since telnet_gate is not a telnet client, those negotiations are not getting answe and the telnet server never gives a login prompt. I have verified I _am_ connecting to the system in question, but these negotiations are not getting completed. The telnet client I am using to connect to Synchronet does not respond to these negotiations becuase it is programmed to do the negotiation during a connect attempt, not while a connect is already done!
The RFC's for telnet are about as bad (reading wise) for any RFC, but I have found that reading these in their entirety either gives me a headache or lea me
well, I think I have found the problem. This problem can actually be dupliacted if you try using telnet_gate into just about any *nix telnetd server, and the problem may be simple or not so simple to correct.
I'm just thinking out loud here, so don't take this as gospel, and correct m where I am wrong, please. (Rob)
Synchronet's telnet server is not doing some of the telnet-protocol communications between server and client that most *nix based telnet server doing.
telnet_gate just opens a pass-thru port to a new IP, and the code yo
posted looks like it is doing just that.
The telnetd on the *nix side,
however, is sending some control questions out to the terminal, expecting to get answers and it is not getting answers. I am assuming my terminal softwa is not sending any answers because it is not listening for those control questions since it _already_ is in a session ( with Synchronet ).
I enabled debugging ( to the screen ) on my unix teletd daemon and made a connection with my telnet client:
----- begin screen paste -----
td: send do AUTHENTICATION
td: recv wont AUTHENTICATION
td: send do TERMINAL TYPE
td: send do TSPEED
td: send do XDISPLOC
td: send do NEW-ENVIRON
td: send do OLD-ENVIRON
td: recv will TERMINAL TYPE
td: recv wont TSPEED
td: recv wont XDISPLOC
td: recv wont NEW-ENVIRON
td: recv wont OLD-ENVIRON
td: recv suboption TERMINAL-TYPE IS "ansi"
td: send will SUPPRESS GO AHEAD
td: send do ECHO
td: send do NAWS
td: send will STATUS
td: send do LFLOW
td: recv do SUPPRESS GO AHEAD
td: recv wont ECHO
td: recv will NAWS
td: recv suboption NAWS 0 80 (80) 0 25 (25)
td: recv dont STATUS
td: recv wont LFLOW
td: send will ECHO
SCO OpenServer(TM) Release 5 (myopia.ujoint.org) (ttyp0)
login: td: recv do ECHO
----- End Screen Paste -----
Wow. That's a lot of crap these two sides are trying to find out. Leaving debugging on and trying to connect through my Synchonet door:
----- Begin Screen Paste -----
Which or Quit: 7
Press Ctrl-] for a control menu anytime.
Connecting to: myopia.ujoint.org
td: send do AUTHENTICATION
----- End Screen Paste -----
Ahah. So, telnetd is waiting for an answer and never gets it. Synchronet won't do it because it is not a telnet client, it's just acting as pass-thru My telnet client ain't gonna answer because it is already in a session with Synchronet!
I am not a C or C++ programmer, but I understand enough to read code and get fair idea. I generally do bourne or bash scripting on unix, work with SQL, program in Visual Basic. This means I know what kind of work could be invol to add code to Synchronet to act as a psuedo-telnet-client and anser the pre-connecting requests, and then drop into a pass-through mode. I know it ain't pretty. If I could suggest something like this happening, then let's I just did.
I've got some C/C++ source here for a telnet client and if I can find the snippets in question, I'll send them your way...
... if you are interested. I'm off finding other telnet clients and testing them to see if it is just my (2) clients acting this way or do they all do t to me...
I am now bald and have a flat spot on my forehead.
I've tried this so many ways I'm still spinning.
What telnet client are you using?
I've tried the Windows 98 included telnet
PowerTerm, and am now going out for others.
I can connect out to vert and talamasca just fine, but if I try to connect t either my internal unix box ( SCO OpenServer 5.0.5 ) or a box on the net whe I have a shell account ( some Red Hat.. uname -a reports version 2.0.38 ) I just hang. netstat -a shows a connection to the system, but my telnet clien hangs there.
I'll keep trying things, but it's getting to the point I'm thinking of putti my unix box up front and have the bbs as a doorway from there.
RE: telnet_gate
BY: Hemo to Digital Man on Wed Sep 20 2000 07:03 pm
I am now bald and have a flat spot on my forehead.
I've tried this so many ways I'm still spinning.
What telnet client are you using?
HyperTerminal PE 5.0
I've tried the Windows 98 included telnet
PowerTerm, and am now going out for others.
I can connect out to vert and talamasca just fine, but if I try to connec either my internal unix box ( SCO OpenServer 5.0.5 ) or a box on the net I have a shell account ( some Red Hat.. uname -a reports version 2.0.38 ) just hang. netstat -a shows a connection to the system, but my telnet cl hangs there.
Did you try modifying telgate.src like I suggested?
I'll keep trying things, but it's getting to the point I'm thinking of pu my unix box up front and have the bbs as a doorway from there.
I don't think that will be necessary.
Rob
I am now bald and have a flat spot on my forehead.
I've tried this so many ways I'm still spinning.
What telnet client are you using?
HyperTerminal PE 5.0
I've tried the Windows 98 included telnet
PowerTerm, and am now going out for others.
I can connect out to vert and talamasca just fine, but if I try to con either my internal unix box ( SCO OpenServer 5.0.5 ) or a box on the n I have a shell account ( some Red Hat.. uname -a reports version 2.0.3 just hang. netstat -a shows a connection to the system, but my telnet hangs there.
Did you try modifying telgate.src like I suggested?
I'll keep trying things, but it's getting to the point I'm thinking of my unix box up front and have the bbs as a doorway from there.
I don't think that will be necessary.
Rob
I have modified talgate.src, I now have the 'telnet_gate str' line reading 'telnet_gate str 16'
err.. telgate.src ... too lazy to edit that line. did a 'baja telgate' and tried it again. Made no difference.. I don't understand why I can telnet i vert and talamasca but not into my shell account or local unix box.
I have also tried Eric's Telnet98, and Tera Term Pro, with no differences. I'll go to Hilgraeve's site later and grab Hyperterm PE and then cross my fingers.
I've put some updated DLLs and TELGATE.SRC/BIN in your .OUT directory. These should fix the problem you're having with Synchronet sucking-up the telnet commands and responses (put these files in your EXEC directory).
I've put some updated DLLs and TELGATE.SRC/BIN in your .OUT directory. These should fix the problem you're having with Synchronet sucking-up the telnet commands and responses (put these files in your EXEC directory).
Oh man... ain't it nice to be using software that's 'actively' being develop
Sysop: | Ree |
---|---|
Location: | Toronto, ON |
Users: | 2 |
Nodes: | 10 (0 / 10) |
Uptime: | 01:51:04 |
Calls: | 369 |
Files: | 2 |
Messages: | 38,903 |