Re: big problem with email

Interesting point.

"Joe" <joe@xxxxxxxxxxxxxx> wrote in message
news:O%23k2bJeiIHA.4844@xxxxxxxxxxxxxxxxxxxxxxx
Mike_in_Nebraska wrote:
If it was me I would attach a workstation to the same router the
external nic of the SBS is installed on. If your SBS external nic is
at 192.168.1.2 and the laptop/workstation attached to your router it
should have an ip of 192.168.1.3 or maybe 1.100. I would then telnet
to 192.168.1.2 25 to see if it answers. With this test you are testing
to see if ISA is causing problems. Actually I would attach a crossover
cable from my laptop to the server external nic and test. This
eliminates your router from the test. Then I would test with the
router in the picture and keep working until I figure out where the
problem is. I keep working until I get to the problem. I will assum
that you did no configuring in ISA as the SBS connect to the internet
wizard is all you have to do to get ISA working.

In Exchange under servers/servername/protocols/default smtp virtual
server properties the ip address hould be all unassigned.

OK. I attached a laptop to my router and gave it a static IP on the
same subnet as the external NIC. From a command prompt, I typed
"telnet 192.168.1.10 25", hit enter and it immediately went to the
command prompt. I next tried "telnet 192.168.1.10:25: and it couldn't
connect. The error is: "Connecting 192.168.1.10 ..... Could not open
connection to the host. on port 23: Connect failed."


Wait a minute, confusion is creeping in here. The first string you typed
is correct, if you get the command prompt straight back then it's being
refused.

If you try telnet without a space after the IP address and then a port
number, it will try port 23, which is the 'well-known' port for the telnet
server. This shouldn't even be installed, let alone running, and the port
certainly should not be open on the SBS external NIC. It's basically an
obsolete logon method using clear text for passwords.

The telnet client is still useful, as it provides a way to 'manually'
connect to a TCP/IP service, and you're using it here to try to reach
Exchange. If you succeed, Exchange will reply with its banner, usually the
version string, and you will be left with a telnet prompt to issue further
instructions. You can actually send an email to an SMTP server this way,
if you know a valid recipient on the server, see the KB article
http://support.microsoft.com/kb/153119 for details.

The return to the command prompt means that something has received the
telnet connection, and isn't going to play. That suggests ISA, so try it
again with the ISA monitoring window open, and you'll almost certainly see
a refusal message. This should give you the necessary clue as to what ISA
is up to and why.


.

Relevant Pages

  • RE: TELNET connection failure
    ... Telnet enabling protocol filter ahead of the SBS Internet Access entry. ... ISA filter was blocking the Telnet access. ... I recommend you to use the CEICW wizard to configure the SBS server ... Please follow the link and download and run the Microsoft Internet ...
    (microsoft.public.windows.server.sbs)
  • Re: moving from 2 NIC to 1 NIC and stop using ISA
    ... Without actually going to the server to look, ... Are you using ISA 2006 on your SBS ... NICs and ISA. ... Is the router going to handle IP assignments now? ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS2003 ISA-Compatible Router suggestions?
    ... take place of the double NICs ISA server 2004. ... if you use the router to take place of the ISA ... On the Connection Type page, click Broadband, and then click Next. ...
    (microsoft.public.windows.server.sbs)
  • RE: TELNET connection failure
    ... I recommend you to use the CEICW wizard to configure the SBS server ... the ISA firewall client will have this problem. ... Can you telnet external from ISA server? ... Please follow the link and download and run the Microsoft Internet ...
    (microsoft.public.windows.server.sbs)
  • Re: ISDN Routers w/ Windows Server 2003
    ... You can do the same with either ISA or Proxy2. ... > network server and to the Internet via the Internet router. ...
    (microsoft.public.isaserver)