Jump to content

Recommended Posts

Guest NexLAN
Posted

I'm not sure if I'm posting in the correct forum or not and if I'm

not

will someone please guide me in the right direction.

 

We have a strange issue going on here. At my desk and at a client's

desk when we go to a command prompt and type telnet smtp.domain.com

110 (or even 25) the banner will appear. Whenever I try to input any

commands it doesn't matter what I type after I type one letter an

automatic carriage return is input after the letter. This same thing

happens on the mail server as well. I'm running Windows XP and so is

the client. We have Windows 2003 on the server. Our mail server is

a

POP3 mail server with multiple domains. It does not matter which

domain we try to telnet to we receive the same response.

 

 

Now, here is where it gets stranger. Two people currently in this

office run Windows Vista and can go to a command prompt and type in

the telnet commands without any problems.

 

 

Any ideas? I even installed Windows XP Service Pack 3 on my computer

for giggles to see if that would work and it did not. Any ideas or

suggestions would be greatly appreciated.

 

 

Thanks!

  • Replies 3
  • Created
  • Last Reply

Popular Days

Guest Jon Knight
Posted

Re: Problems with Telnet

 

Try a utility called "Putty"

 

"NexLAN" <lisa@nexlan.com> wrote in message

news:cbee4f94-5114-4817-b717-dd6c2ecbe4bb@34g2000hsf.googlegroups.com...

> I'm not sure if I'm posting in the correct forum or not and if I'm

> not

> will someone please guide me in the right direction.

>

> We have a strange issue going on here. At my desk and at a client's

> desk when we go to a command prompt and type telnet smtp.domain.com

> 110 (or even 25) the banner will appear. Whenever I try to input any

> commands it doesn't matter what I type after I type one letter an

> automatic carriage return is input after the letter. This same thing

> happens on the mail server as well. I'm running Windows XP and so is

> the client. We have Windows 2003 on the server. Our mail server is

> a

> POP3 mail server with multiple domains. It does not matter which

> domain we try to telnet to we receive the same response.

>

>

> Now, here is where it gets stranger. Two people currently in this

> office run Windows Vista and can go to a command prompt and type in

> the telnet commands without any problems.

>

>

> Any ideas? I even installed Windows XP Service Pack 3 on my computer

> for giggles to see if that would work and it did not. Any ideas or

> suggestions would be greatly appreciated.

>

>

> Thanks!

>

>

Guest NexLAN
Posted

Re: Problems with Telnet

 

On May 20, 9:07 am, "Jon Knight" <jonkni...@saber.eclipse.co.uk>

wrote:

> Try a utility called "Putty"

>

> "NexLAN" <l...@nexlan.com> wrote in message

>

> news:cbee4f94-5114-4817-b717-dd6c2ecbe4bb@34g2000hsf.googlegroups.com...

>

>

>

> > I'm not sure if I'm posting in the correct forum or not and if I'm

> > not

> > will someone please guide me in the right direction.

>

> > We have a strange issue going on here.  At my desk and at a client's

> > desk when we go to a command prompt and type telnet smtp.domain.com

> > 110 (or even 25) the banner will appear.  Whenever I try to input any

> > commands it doesn't matter what I type after I type one letter an

> > automatic carriage return is input after the letter.  This same thing

> > happens on the mail server as well.  I'm running Windows XP and so is

> > the client.  We have Windows 2003 on the server.  Our mail server is

> > a

> > POP3 mail server with multiple domains.  It does not matter which

> > domain we try to telnet to we receive the same response.

>

> > Now, here is where it gets stranger.  Two people currently in this

> > office run Windows Vista and can go to a command prompt and type in

> > the telnet commands without any problems.

>

> > Any ideas?  I even installed Windows XP Service Pack 3 on my computer

> > for giggles to see if that would work and it did not.  Any ideas or

> > suggestions would be greatly appreciated.

>

> > Thanks!- Hide quoted text -

>

> - Show quoted text -

 

I need to telnet to see the exact error message and why the e-mail

won't be setup. That is why I've been using telnet in the past and it

always worked up until a few days ago.

Guest Jon Knight
Posted

Re: Problems with Telnet

 

yes putty is a telnet client

 

"NexLAN" <lisa@nexlan.com> wrote in message

news:144c6f9e-e510-4f38-b780-b880e2866463@e53g2000hsa.googlegroups.com...

On May 20, 9:07 am, "Jon Knight" <jonkni...@saber.eclipse.co.uk>

wrote:

> Try a utility called "Putty"

>

> "NexLAN" <l...@nexlan.com> wrote in message

>

> news:cbee4f94-5114-4817-b717-dd6c2ecbe4bb@34g2000hsf.googlegroups.com...

>

>

>

> > I'm not sure if I'm posting in the correct forum or not and if I'm

> > not

> > will someone please guide me in the right direction.

>

> > We have a strange issue going on here. At my desk and at a client's

> > desk when we go to a command prompt and type telnet smtp.domain.com

> > 110 (or even 25) the banner will appear. Whenever I try to input any

> > commands it doesn't matter what I type after I type one letter an

> > automatic carriage return is input after the letter. This same thing

> > happens on the mail server as well. I'm running Windows XP and so is

> > the client. We have Windows 2003 on the server. Our mail server is

> > a

> > POP3 mail server with multiple domains. It does not matter which

> > domain we try to telnet to we receive the same response.

>

> > Now, here is where it gets stranger. Two people currently in this

> > office run Windows Vista and can go to a command prompt and type in

> > the telnet commands without any problems.

>

> > Any ideas? I even installed Windows XP Service Pack 3 on my computer

> > for giggles to see if that would work and it did not. Any ideas or

> > suggestions would be greatly appreciated.

>

> > Thanks!- Hide quoted text -

>

> - Show quoted text -

 

I need to telnet to see the exact error message and why the e-mail

won't be setup. That is why I've been using telnet in the past and it

always worked up until a few days ago.


×
×
  • Create New...