Re: POP3 Publishing - Publish server on same subnet as source? Workaro

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


Richard if your clients need to get email from a server on the internet then they need internet access and you need an access rule that allows this type of communication. Your users will need to be either securnat clients or firewall clients. Publishing rules are for allowing access to an internal resource and making it available to the external network.

"Richard" <Richard@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4A074A5A-443A-4C26-9999-C964E1CC2DC1@xxxxxxxxxxxxxxxx
I read somewhere that you cannot publish a server on the same subnet as the
source IP is this a true limitation of ISA 2006? If it is not possible what
would be a good work around for this?

I am trying to publish a POP3 server internally but it does not work. The
rule does not trap the request at all. The default rule Catches the request
and then denies the request. I am wondering if this is why.

I need to do this because:
All my DNS points at the same DNS name for OWA, POP3, SMTP, etc. Internally
the DNS pointer points straight at the ISA server so that clients do not need
to have Internet access for their mail to work.

Current ISA Rule Configured as:

I created a Mail Server Publishing Rule:
Enabled
Action Allow
POP3 Server
From Anywhere
To IP 10.248.22.19
Listening on Internal Netwrok and Local Host


Client Configured:

When deployed the clients will be using the same DNS name to specify the
POP3 as the SMTP in the mail profile. Currently I am not in production and I
just point at the IP Address for the ISA server in the POP3 specification of
the client mail.



.

Relevant Pages

  • Re: ISA Server Problems, please help
    ... > clients are unaffected, is it secureNAT clients which are affected? ... then checked Send the original host header to the publishing server instead ... > provided unrestricted internet access. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server Problems, please help
    ... Based on the rules you have listed, SecureNAT clients should only be allowed ... The All access rule for SBS Internet Users ... Web Proxy and/or Firewall Client ... > header to the publishing server instead of the actual one. ...
    (microsoft.public.windows.server.sbs)
  • Re: After installing SBS 2003 two IE 6.0.29 SP2 clients that cannot to companyweb
    ... Mozilla, and other clients can access the http://comanyweb, the SBS server ... Reset the Internet Explorer Settings to Default. ... DHCP was turned off in SBS 2003. ...
    (microsoft.public.windows.server.sbs)
  • Re: Firewall Beginners Assistance
    ... make primary internet access on port 8081 ... clients could update the browser using .pac files ... DNS - so, it might be wise to use it anyway. ... why owning a DNS server?? ...
    (comp.security.firewalls)
  • Re: Clients cant browse the web after apply SBS2K3 SP1
    ... different issue and solutions and this newsgroup is for English version ... we must check if the DNS server works properly. ... >Subject: Re: Clients can't browse the web after apply SBS2K3 SP1 ... The error is "Internet explorer can't open the search page". ...
    (microsoft.public.windows.server.sbs)