Re: IP Blocker in SBS2003 exchange

I consult to this company and the user happens to be the MD. He likes doing
things the way he does them, and "it is not ours to question why, but to do
or die"...

Thanks to all for your help with this...

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:O6IwFdcnFHA.576@xxxxxxxxxxxxxxxxxxxxxxx
>
>
> In news:e3$4GjWnFHA.1212@xxxxxxxxxxxxxxxxxxxx,
> Tony <td24601@xxxxxxxxxxxx> typed:
>> Thanks for the reply.
>>
>> I don't mind you asking about why OE. basically the user does not
>> like how OWA or Outlook works (he likes seeing the bars go accross
>> the send/receive dialogue box).
>
> I understand, but your company's mail access methodology should not be
> dictated by users, honestly. He's losing out on most of Exchange's
> features, you can't guarantee his mail will even stay on the server. I
> discourage this ...in fact, I have no place where I permit it. I'm kinda
> mean like that. People put up with me being bossy because their stuff
> works well when they let me do things my way. I suspect this is a training
> issue....try showing him how OL2003 and cached mode make things faster,
> and give him access to public folders, his calendar, out of office,
> etc.... RPC over HTTPs is very nice indeed.
>
>> 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.
>
> Yep.
>
>> The
>> problem I'm having is that this one user cannot telnet in from the
>> one place via port 25, something is stopping his PC from connecting,
>> but he can connect to port 110.
>
> The ISP probably blocks it.
>>
>> What I mean by change the internet is that he has ADSL connection as
>> well as another wireless broadband connection. The ADSL is the one
>> that is stopping him from sending emails and telnetting to port 25. When
>> he connects to the wireless broadband he can send and receive as
>> normal as well as telnet to port 25.
>>
>> if have not setup his IP address in the "all but the list below"
>> area...
>
> It wouldn't matter, because he can't get to your server anyway. You can
> telnet without being permitted to relay, and if you can't telnet, you sure
> can't relay. :)
>>
>>
>> "Lanwench [MVP - Exchange]"
>> <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:uJcRmSWnFHA.3900@xxxxxxxxxxxxxxxxxxxxxxx
>>>
>>>
>>> In news:uDicdAWnFHA.764@xxxxxxxxxxxxxxxxxxxx,
>>> Tony <td24601@xxxxxxxxxxxx> typed:
>>>> Hi,
>>>>
>>>> I have a problem with Outlook Express users sending mail through
>>>> Exchange 2003 on SBS2003.
>>>
>>> Ooh, but do you mind if I ask why you have Outlook Express users?
>>>
>>>> Basically, the user can send emails from all places he needs to (ie,
>>>> home, office etc) except one. He can receive emails alright, but
>>>> when he goes to send it comes up with a cannot find server error.
>>>> If I telnet to the server (telnet <FQDN> 110) it works,
>>>
>>> That just tells you it's listening for POP connections. Not relevant.
>>>
>>>> but if I
>>>> telnet <FQDN> 25 it can't find the server.
>>>
>>> If you telnet on port 25 to the NetBIOS name of the server, what
>>> happens? What TCP/IP address is the SMTP virtual server listening on?
>>>
>>>> The FQDNs are the same.
>>>
>>>> If I change the internet connection, it works fine.
>>>
>>> Change it to what? Where is this?
>>>
>>>> I am thinking that the Virtual SMTP server is blocking this one IP
>>>> address from sending even though it is setup to connect if
>>>> authenticated.
>>>
>>> Possibly, but it seems unlikely unless you're getting an error in
>>> your POP client.
>>>
>>>
>>>> Is there an IP Blocker in a standard install of SBS2003?
>>>
>>> Sure, if you added his IP address and said "all but the list
>>> below"...which seems unlikely.
>>>
>>>> Or, what else could be causing this?
>>>
>>> Why have users use OE/POP anyway? I disable it by default....OWA, or
>>> Outlook, my friend. :)
>>>>
>>>> thanks in advance..
>>>> Tony Dawes.
>
>


.

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: Cant connect to port 25 from another system
    ... port 25 and did a make to update sendmail.cf. ... restarted sendmail. ... When I attempt to telnet to port 25 the connection fails. ... on where outbound smtp connections are okay but smtp sessions ...
    (Fedora)
  • 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)