Re: telnet port 25

Hi,

In addition to what Bharat said, you might also try using a network sniffer,
such as Network Monitor, to capture the network traffic for your failed
telnet attempts. With such a capture, you can see what's happening on the
wire.

You can also use Netcap, a command-line capture tool, to capture packets.
See
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/9e5943e4-8f6e-4b06-bfed-c16dbf89c676.mspx.

Hope this helps.

--
Scott Schnoll
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.


"Bharat Suneja" <bharatsuneja@xxxxxxxxxxx> wrote in message
news:O56ivMLuFHA.3740@xxxxxxxxxxxxxxxxxxxxxxx
> Perhaps. Something between the client and the server. Can the client
> telnet to ANY other smtp server anywhere on port 25? If yes, you rule out
> anything at the client end as well. Now you can be certain it's between
> the client and the particular server.
>
> --
> Bharat Suneja
> MCSE, MCT
> --------------------------------
>
> "Steven" <Steven@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:E7B1260F-6DCF-42F4-9F0E-006C9FEBD579@xxxxxxxxxxxxxxxx
>> good point i tried that and it did work. so could it be a firewall
>> related
>> issue?
>>
>> "Bharat Suneja" wrote:
>>
>>> Can you telnet to smtp from the Exchange server itself? If yes, it means
>>> your service and smtp virtual server are running, and the problem is on
>>> the
>>> network... or the client.
>>>
>>> If you can't, check in ESM if the smtp vs is running. (The service
>>> could be
>>> running, but the vs could be stopped... ).
>>>
>>> --
>>> Bharat Suneja
>>> MCSE, MCT
>>> --------------------------------
>>>
>>>
>>> "Steven" <Steven@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>>> news:E75F665F-DC8E-49F1-A242-47BE94DE3CE5@xxxxxxxxxxxxxxxx
>>> > trying to telnet port 25 "exchange2k" i get this
>>> > Microsoft Telnet> open 192.168.0.228 25
>>> > Connecting To 192.168.0.228...Could not open connection to the host,
>>> > on
>>> > port
>>> > 25:
>>> > Connect failed
>>> > Microsoft Telnet>
>>> > I can however telnet port 110 with no problems. all services are up
>>> > and
>>> > this
>>> > does not matter if i am behind the firewall or in front of it with a
>>> > vpn
>>> > connection. anyone got any clues on this one?
>>> >
>>>
>>>
>>>
>
>


.

Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)
  • RE: Private addresses on public network
    ... anybody accesses those computers from an external network," -- even when the ... JavaScript delivered to the client that causes the client to retrieve ... the attacker, the request results in another JavaScript response that tells ... Moving beyond a single server ...
    (Security-Basics)