Re: IP Blocker in SBS2003 exchange

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).
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. 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.

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...


"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: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • RE: VBscript Error on SBS2k3
    ... DHCP Server turned of SonicWALL with VPN Pass through request for IP to ... the problem should be caused by the 4125 port. ... > | Accessories and Communications and Remote Desktop Connection? ... > | 2.In Internet Explorer on the workstation you are connecting from, ...
    (microsoft.public.windows.server.sbs)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Can not access Web and FTP sites from Internet
    ... your IP Configuration on the Server is correctly. ... Connecting To 12.208.215.87...Could not open connection to the host, ... 1> From the result, we can see the telnet failed, which means the router ... does not forward Port 443 to SBS Server. ...
    (microsoft.public.windows.server.sbs)