Re: no incoming email

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Les Connor [SBS Community Member] (les.connor_at_DEL.cfive.ca)
Date: 12/23/04

Next message: Steve Foster [SBS MVP]: "Re: SQL Versions and Hotfixes"
Previous message: Frank McCallister SBS MVP: "Re: no incoming email"
In reply to: Marcia: "Re: no incoming email"
Next in thread: Marcia: "Re: no incoming email"
Reply: Marcia: "Re: no incoming email"
Messages sorted by: [ date ] [ thread ]

Date: Wed, 22 Dec 2004 19:19:40 -0600

Marcia,

Telnet on port 23 proves nothing. Try and telnet on port 25, there is no
answer.

did you get all the tests I ran previously, posted to one of your older
threads ?

I still cannot get a connection on port 25, and a port scan doesn't show it
responding either. I can't believe MS cannot tell you the port is not open
or responding, or that they'd make you wait until after Christmas. That's
ridiculous.

If the SBS is configured correctly, and the ISP is positive there are no
problems on his end, then that leaves the router as a prime suspect.

-- 
Les Connor [SBS Community Member]
-----------------------------------------------------------
SBS Rocks !
"Marcia" <mkp@1248.com> wrote in message 
news:eGMlXTH6EHA.2316@TK2MSFTNGP15.phx.gbl...
> Yes I have.  Telnet doesn't work, I get "connection to host lost".  Yet, 
> when I login to the router, I get the following:
>
>
> #ip nat trans
> ; error -121: illegal operation
> #show ip nat trans
> LAN IP address--Port--WAN IP address--Port--Rem IP 
> Address--Port--Dir-Prot-h:mm
>  192.168.3.101:54408 209.195.154.157:61074  216.83.180.138:80    out TCP
> >10h
>  192.168.3.101:54386 209.195.154.157:61056  207.46.245.156:80    out TCP
> >10h
>  192.168.3.101:54409 209.195.154.157:61075  216.83.180.138:80    out TCP
> >10h
>  192.168.3.101:54275 209.195.154.157:61025  216.207.61.196:80    out TCP
> >10h
>  192.168.3.101:54340 209.195.154.157:61038  192.168.52.100:161   out UDP 
> 1s
>  192.168.3.101:54340 209.195.154.157:61039  192.168.53.100:161   out UDP 
> 25s
>  192.168.3.101:3003  209.195.154.157:61015   198.190.226.3:53    out UDP 
> 0:02
>  192.168.3.101:54404 209.195.154.157:61070   64.154.80.197:80    out TCP
> >10h
>  192.168.3.101:53287 209.195.154.157:60460    208.22.33.46:80    out TCP
> >10h
>  192.168.3.101:54268 209.195.154.157:61022     66.18.100.2:80    out TCP
> >10h
>  192.168.3.101:25    209.195.154.157:25     68.162.151.136:1569  in  TCP 
> 7s
>  192.168.3.101:54373 209.195.154.157:61045     66.18.100.2:80    out TCP
> >10h
>  192.168.3.101:54402 209.195.154.157:61068  207.68.178.238:80    out TCP
> >10h
>  192.168.3.101:54403 209.195.154.157:61069  207.68.178.238:80    out TCP
> >10h
>  192.168.3.101:54401 209.195.154.157:61067    81.52.248.15:80    out TCP
> >10h
>  192.168.3.101:54398 209.195.154.157:61064    81.52.248.41:80    out TCP
> >10h
>  192.168.3.100:23    209.195.154.157:23      24.154.49.184:1093  in  TCP
> >10h
>  192.168.3.101:54276 209.195.154.157:61026   66.18.100.113:80    out TCP
> >10h
>  192.168.3.101:54407 209.195.154.157:61073    81.52.248.71:80    out TCP
> >10h
>  192.168.3.101:54247 209.195.154.157:61008  65.119.205.137:80    out TCP
> >10h
>  192.168.3.101:49787 209.195.154.157:57807    208.22.33.46:80    out TCP
> >10h
> Total entries in NAT cache: 21
> #show ip nat trans
> LAN IP address--Port--WAN IP address--Port--Rem IP 
> Address--Port--Dir-Prot-h:mm
>  192.168.3.101:54408 209.195.154.157:61074  216.83.180.138:80    out TCP
> >10h
>  192.168.3.101:54409 209.195.154.157:61075  216.83.180.138:80    out TCP
> >10h
>  192.168.3.101:54275 209.195.154.157:61025  216.207.61.196:80    out TCP
> >10h
>  192.168.3.101:25    209.195.154.157:25      209.195.133.6:4445  in  TCP 
> 4s
>  192.168.3.101:3003  209.195.154.157:61015   198.190.226.3:53    out UDP 
> 0:01
>  192.168.3.101:54404 209.195.154.157:61070   64.154.80.197:80    out TCP
> >10h
>  192.168.3.101:53287 209.195.154.157:60460    208.22.33.46:80    out TCP
> >10h
>  192.168.3.101:54268 209.195.154.157:61022     66.18.100.2:80    out TCP
> >10h
>  192.168.3.101:54373 209.195.154.157:61045     66.18.100.2:80    out TCP
> >10h
>  192.168.3.101:54402 209.195.154.157:61068  207.68.178.238:80    out TCP
> >10h
>  192.168.3.101:54403 209.195.154.157:61069  207.68.178.238:80    out TCP
> >10h
>  192.168.3.101:54401 209.195.154.157:61067    81.52.248.15:80    out TCP
> >10h
>  192.168.3.101:54398 209.195.154.157:61064    81.52.248.41:80    out TCP
> >10h
>  192.168.3.100:23    209.195.154.157:23      24.154.49.184:1093  in  TCP
> >10h
>  192.168.3.101:25    209.195.154.157:25        24.154.1.24:43760 in  TCP 
> 3s
>  192.168.3.101:54407 209.195.154.157:61073    81.52.248.71:80    out TCP
> >10h
>  192.168.3.101:54247 209.195.154.157:61008  65.119.205.137:80    out TCP
> >10h
>  192.168.3.101:49787 209.195.154.157:57807    208.22.33.46:80    out TCP
> >10h
> Total entries in NAT cache: 18
> #
>
> Notice 4 lines up is the email that attempted to come in.
>
> #show ip nat trans
> LAN IP address--Port--WAN IP address--Port--Rem IP 
> Address--Port--Dir-Prot-h:mm
>  192.168.3.101:54437 209.195.154.157:61094   66.18.100.113:80    out TCP
> >10h
> 209.195.154.157:445   209.195.154.157:445    209.195.116.34:1450  in  TCP 
> 26s
>  192.168.3.101:53287 209.195.154.157:60460    208.22.33.46:80    out TCP
> >10h
>  192.168.3.101:54268 209.195.154.157:61022     66.18.100.2:80    out TCP
> >10h
> 209.195.154.157:445   209.195.154.157:445     209.195.72.84:2469  in  TCP 
> 29s
>  192.168.3.101:54373 209.195.154.157:61045     66.18.100.2:80    out TCP
> >10h
>  192.168.3.101:54447 209.195.154.157:61095     66.18.100.2:80    out TCP
> >10h
>  192.168.3.101:54398 209.195.154.157:61064    81.52.248.41:80    out TCP
> >10h
>  192.168.3.101:54247 209.195.154.157:61008  65.119.205.137:80    out TCP
> >10h
>  192.168.3.100:23    209.195.154.157:23      24.154.49.184:1129  in  TCP
> >10h
>  192.168.3.101:49787 209.195.154.157:57807    208.22.33.46:80    out TCP
> >10h
> Total entries in NAT cache: 11
> #
>
> Notice 3 lines up lets me telnet in.
>
> Any other ideas would be greatly appreciated.  Thanks.
>
> Marcia
>
>
> "Bradley Dinerman [MVP - Windows Networking]" 
> <NewsPost@DoNotSpam.neisg.org.DoNotSpam> wrote in message 
> news:OUyrJzG6EHA.616@TK2MSFTNGP09.phx.gbl...
>> Are you certain that mail from the outside is reaching the inside?  Have 
>> you done a TELNET to port 25 of your system from the Internet using the 
>> public IP address of your mail server?  What about by DNS name?
>>
>>
>> ______________________________________
>> Bradley J. Dinerman, MVP - Windows Server Systems
>> President, New England Information Security Group
>> http://www.neisg.org
>>
>> Marcia wrote:
>>> Hi!  After several hours with MS PSS, I still have no incoming email. 
>>> We left it with follow up phone meeting on Monday after Christmas.  The 
>>> manufacturer of our router showed me messages coming into the router. 
>>> Our ISP says they only get held on their backup server if our server 
>>> doesn't accept them.
>>>
>>> MS spent some considerable time verifying DNS and ISA, Exchange and IIS 
>>> and saw no reason that they weren't coming through.
>>>
>>> My question to this group is twofold:
>>> 1.  Is there anything within remote connections, the external nic, or 
>>> other routing mechanism besides ISA that will reject it?
>>> 2.  Are there logs on the server that verifies that email came in?
>>>
>>> Thanks.
>>>
>>> Marcia
>>>
>

Next message: Steve Foster [SBS MVP]: "Re: SQL Versions and Hotfixes"
Previous message: Frank McCallister SBS MVP: "Re: no incoming email"
In reply to: Marcia: "Re: no incoming email"
Next in thread: Marcia: "Re: no incoming email"
Reply: Marcia: "Re: no incoming email"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: IIS and SBS 2003
... I have a new sbs2003 install and if I telnet to localhost ... port 80, and type hhh and hit enter it returns a HTTP/1.1 400 Bad ... "broken" sbs server, it connects but then dumps me. ... If I http to localhost, companyweb or anything I get Cannot Find ...
(microsoft.public.windows.server.sbs)
Re: Suggestion for a lexical (login mode via TCPIP)
... Not sure of it is the right one to modify or to add another one, but it would be useful to be able to get information on whether the user us coming in via FTP, TELNET, etc. ... This would also allow a LOGIN.COM to check if someone is coming in through a secure/SSL port for instance. ... For the HP SSH server, it seems to be undefined. ... forget about the possibility of virtual terminals. ...
(comp.os.vms)
Re: RDP access to SBS 2003 - HELP please
... Might I add that 'out of the box', when I first got the server it worked ... of it to the telnet prompt and quit. ... Try the remote desktop connection to see if it works. ... the effect that it can't connect to xxx.xxx.xxx.xxx port 23. ...
(microsoft.public.windows.server.sbs)
Re: IP Blocker in SBS2003 exchange
... > What I was trying to explain in the telnet section was that I realise ... > the server is listening for connections on ports 110 and 25. ... > but he can connect to port 110. ... > well as another wireless broadband connection. ...
(microsoft.public.windows.server.sbs)
Re: User access form remote Site ove managed VPN
... I think you have the syntax wrong in your telnet command. ... If you try and use a colon, it defaults to port 23 which is why you got ... the basic directions for implementing a terminal server on SBS2003 domain. ... managed VPN link between remote sites and headoffice. ...
(microsoft.public.windows.terminal_services)