Re: telnet: could not resolve

2003-06-24 Thread Colin Watson
ost port. > > > > Since i upgraded to sarge on few machines "telnet 0 port" dont work: > > > > 1 [EMAIL PROTECTED]:kolisko$ telnet 0 25 > > telnet: could not resolve 0/25: Name or service not known > > 1 [EMAIL PROTECTED]:kolisko$ telnet localhost 25

Re: telnet: could not resolve

2003-06-24 Thread Shawn Lamson
nes "telnet 0 port" dont work: > > 1 [EMAIL PROTECTED]:kolisko$ telnet 0 25 > telnet: could not resolve 0/25: Name or service not known > 1 [EMAIL PROTECTED]:kolisko$ telnet localhost 25 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]

Re: telnet: could not resolve

2003-06-23 Thread Shyamal Prasad
"Nathan" == Nathan Poznick <[EMAIL PROTECTED]> writes: Nathan> Use localhost when you mean localhost? I wasn't aware Nathan> that '0' was valid shorthand for localhost. Actually it is. From RFC 1700 ("Assigned Numbers") (a) {0, 0} This host on this network. Can on

Re: telnet: could not resolve

2003-06-23 Thread Nathan Poznick
Thus spake Michal Kolesar: > Hi all, > > i am using on all woody machines commands like "telnet 0 25" or "telnet > 0 110" for telnet to localhost port. > > Since i upgraded to sarge on few machines "telnet 0 port" dont work: > Any idea? Use localhost when you mean localhost? I wasn't aware that

telnet: could not resolve

2003-06-23 Thread - = k o l i s k o = -
Hi all, i am using on all woody machines commands like "telnet 0 25" or "telnet 0 110" for telnet to localhost port. Since i upgraded to sarge on few machines "telnet 0 port" dont work: 1 [EMAIL PROTECTED]:kolisko$ telnet 0 25 telnet: could not resolve 0/25: Name

telnet: could not resolve

2003-06-23 Thread Michal Kolesar
Hi all, i am using on all woody machines commands like "telnet 0 25" or "telnet 0 110" for telnet to localhost port. Since i upgraded to sarge on few machines "telnet 0 port" dont work: 1 [EMAIL PROTECTED]:kolisko$ telnet 0 25 telnet: could not resolve 0/25: Name