Re^2: DBI Proxy connection prob

What does the Telnet test tell me?
Here is the attempt...

C:\erick>telnet isfe 3333
Connecting To isfe...Could not open a connection to host on port 3333 
+: Connect
failed
[download]

If I don't have a telnet service accepting connections on 3333, how would this test ever work?

Update:
However, running the telnet command with out the port does work.



SunOS 5.9

login: erickn
Password:
Last login: Mon Oct  4 16:30:59 from rmtislt054.csc.
erickn@isfe:/home/erickn> exit


Connection to host lost.

C:\Documents and Settings\erickn>
[download]

but doesn't that just test the default telnet port (whatever that is)?

Comment on Re^2: DBI Proxy connection prob Select or Download Code

Replies are listed 'Best First'.
Re^3: DBI Proxy connection prob by tachyon (Chancellor) on Oct 04, 2004 at 23:44 UTC
You are confusing telnet the client program and telnet the protocol/server. They are different. Telnet the program is just making a socket connection for you and displaying the IO in a shell type environment. You can't get a connection on 3333 which is the problem. Your script will fail to get a socket on 3333 as well. FIREWALL or DEAD DEAMON is the reason it does not work. Anyway telnet can connect to any socket server, You can telnet into your SMTP server on 25, HTTP server on 80, POP3 server on 110 or any other socket server on any other port. If you know the protocol you can talk to them. For example I can send myself email via telnet (the program, not the protocol/server) connecting to an SMTP server on port 25 because I know the protocol (I typed the HELO, MAIL FROM, RCPT TO, DATA, blah . , QUIT lines). Knowing basic SMTP and POP3 etc is often useful to debug connectivity issues FWIW. Rather than just ping you telnet into the server and say Gday. Read more... (1235 Bytes)	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: DBI Proxy connection prob
by tachyon (Chancellor) on Oct 04, 2004 at 23:44 UTC

You are confusing telnet the client program and telnet the protocol/server. They are *different*. Telnet the program is just making a socket connection for you and displaying the IO in a shell type environment. You can't get a connection on 3333 which is the problem. Your script will fail to get a socket on 3333 as well. FIREWALL or DEAD DEAMON is the reason it does not work. Anyway telnet can connect to any socket server, You can telnet into your SMTP server on 25, HTTP server on 80, POP3 server on 110 or *any other socket server on any other port*. If you know the protocol you can talk to them. For example I can send myself email via telnet (the program, not the protocol/server) connecting to an SMTP server on port 25 because I know the protocol (I typed the HELO, MAIL FROM, RCPT TO, DATA, blah . , QUIT lines). Knowing basic SMTP and POP3 etc is often useful to debug connectivity issues FWIW. Rather than just ping you telnet into the server and say Gday.