October 28th, 2001, 12:16 PM
Well you could say I'm a newbie, although I have suficient knowledge of computers and multimedia. And I was just wondering if anyone could help me out with telnet. I've been tryin telnet in windows from cmd, but it never successfully connects. bawling I was wondering if it is just m$ windows or somthing else that was causing this. Im running Windows 2000 Pro, on a 56k modem. I have Norton Internet Security and Blackice defender running. Is it possible that one or both of these programs could be causing the connection failure? If so how do i stop this?
Well thanks in advance.
October 28th, 2001, 12:35 PM
Are you sure that the site you're trying to telnet to is up and running?When you use the telnet what is the exact syntax that you are typing?
It's possible that both Norton's and BID are blocking telnet. You have to enable outbound connections. Generally they shouldn't be blocking things but you may have them set to paranoid and thus, they'd probably prevent it. Check to see that you are enabling outbound access to port 23.
Anyways, hope this helps.
October 28th, 2001, 01:23 PM
Here you go
Ok yeah with telnet for windows, if youre using the 98 edition you get the original cool one with a GUI interface.Even though 2000 doesn't have it. Most of the time It will get hunk up, and somtimes it will even say couldn't connect to host. Try looking up for Terminal Emulation Applications.
For example if you go to download.com you can get Putty.exe which is great. Absolute Telnet which is ok. ZOC i really like because you can run programs with ease. There are alot more but I strongly recomend using a different telnet application.
What Ms Mittens was saying is correct if you have a firewall up like Norton you have to allow out going connections. So you can telnet, or else you will get error messages. Set them so you can still block incoming, but so you can make an outgoing connection.
90% of the time it will be your firewall.
Hope it helps, I strongly recomend geting putty.
October 30th, 2001, 07:35 AM
You might also want to run a trace route on the address your trying to telnet as something may be blocking your connection elsewhere. I experienced this where my old ISP had blocked telnet the telnet port on the server *dodgy backyard ISP's*...
In cmd, simply type
Nice n simple tracert.. although not very pretty...
If you want a pretty one, get your hands on a copy of NeoTracePro, which also gets other information for you at the same time....
Hope that helps
October 30th, 2001, 09:05 AM
October 30th, 2001, 11:55 AM
Hrmm. Have you tried telneting from another OS? That error is usually indicative of the server (the place you are telnetting to) not having telnet access available. Are you sure it is on? Perhaps they have a firewall that's preventing access? Perhaps they have ping turned off? (Telnet sorta needs ping)
October 30th, 2001, 05:01 PM
Ok.. if you disabled both programs..
and you are attempting to telnet and its not working its because of two things...
One.. (Is the server your connecting to on a different port?)
two.. (The server is down.)
Hackers are impervious. Resistant is futile.
October 30th, 2001, 05:23 PM
What type of OS are trying to telnet too? Perhaps the inetd has been disabled on the Server you are trying to connect too. Also try to telnet to IP specific instead of hostname, if you haven't tried that already.
\"Disciples, like diamonds, are developed in a process of time and heavy pressures, and both the disciple and the diamond reflect and magnify the light that comes through them.\"
Neal A. Maxwell