Actually, the way I have this set up is as follows:

Two internal nics, both with private IP's.  The gateway for the .1 nic is
the router, the gateway for the .2 nic being the .1.  The problem I am
having is that mail works fine internally.  I can send mail, receive mail to
both internal and external personnel.  The problem I have is with Outlook
settings outside the network.  When I dial up through an ISP, I use the IP
address (public) of the router to connect to the Imail server.  However,
when I connect, I am able to send mail, but not able to receive mail.

Although your proposed solution is probably the best one, this is for a
client, and spending more money, unless the current hardware will NOT work,
is not an option.  I know this configuration will work, but I am missing
something simple.

-----Original Message-----
From: Pablo Ruiz Perez [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 3:21 AM
To: [EMAIL PROTECTED]
Subject: RE: [IMail Forum] Imail & Proxy 2.0





Let me first give you a brief description of the hardware and software
involved in my problem.

One server running NT Server, SP5, Imail, Proxy 2.0, also serving as the PDC
with dual nic's, both with private IP's, 192.168.0.1 and 192.168.0.2.  The
.1 nic runs to a Lucent Pipeline 50 ISDN router, the .2 to the workgroup
hub.  The problem I am having is this:  My remote offices are configured to
use Imail via Outlook Express and can send messages but cannot receive them.
The router has the correct ports open and forwarding to the .1 address.  I
am able to telnet into port 110 locally, but not into port 110 from the
outside.  Any ideas?  If you need more information, let me know and I'll be
glad to provide.  Thanks.

   Let me stop a little bit with this info, and explain what you have:

  - You've got one Imail server with 2 IPs, one external and one internal
  - The Imail machine is your PDC, so primary IP is the internal one �OK?
  - Your internal machines can POP3 to your internal IP, but can't POP3 to
your external one (�Imail's one?)
  
  I had one similar problem with a similar configuration.

  I went from the enterprise after resolving some of these problems, this
couldn't...

  You've got this configuration

    <Imail-PDC>------Router ------- External
        |
       Hub
        |
        Machines

  Posible causes:
   c1) You have to assign an IP to your domain in Imail, maybe you're
working with Imail only in the internal IP, and not in the external one.
   s1) Don't know how Imail will work with the same domain doubled into two
IPs

   c2) You've got dom.com (name of your computer [DNS server]) as SMTP and
POP3, and externally had to work, but internally not.
     Or: You've got IMAILSERVERPDC (name of your computer [WINS server or
MB]), and when you go externally, it won't work
   s2) This is really dificult, and the possible solution is to have two
profiles in Outlook, one internal, and one external, configuring diferent
for one or another
   s2.2) UPGRADE YOUR SYSTEM, and have one Imail server with an external IP,
and one PDC with ONLY INTERNAL IP

   c3) Are you routing correctly the POP3 port from the Lucent Router? Maybe
it is doing NAT to your network, and you need some extra work to route the
POP3. Have you got some public internet address, or you just have Lucent
one, shared with Imail?
   s3) Time will say ...

   c4) The one I saw. You connect to the external IP, and the IP that
responds you is the primary one of the machine. That's the internal one. And
can make your system work at half, some program's doesn't like the server IP
change in the negociation of the comunication.
   s4) UPGRADE YOUR SYSTEM in two machines

    I greatly recomend to have a configuration like this:

                     Router
                       �
              (  Firewall machine )
              (  Internal router  )  ------ Imail server - proxy server -
web server (all the machines with external IP's)
                       �
                       �
                Internal network - PDC - BDCs - Printing servers - File
servers - Db servers - (all servers with internal IPs)

   In this configuration, a three way firewall configuration, you can
protect all your private network very hard, and have some access from
outside to your internet machines. The problem is that you'll need to buy
two machines, one for firewalling, and one for Imail (or PDC, whatever
you'll like to reinstall). I encourage you to try this configuration.

   And after all, always try to have the machines with only one IP in the
internal network, on top your PDC.

   Hope this may help


> Christopher Conley
> Field Service Engineer
> CyberNET Engineering
> 25 S. Division
> Grand Rapids, MI 49503
> Direct Dial: 616.913.2686
> FAX: 616.913.2913
> Page: 616.478.6737
> mailto:[EMAIL PROTECTED]
> 
> **************************************************************************
> ***
> The information in this email is confidential and may be legally
> privileged.
> It is intended solely for the addressee. Access to this email by anyone
> else
> is unauthorized. 
> 
> If you are not the intended recipient, any disclosure, copying,
> distribution
> or any action taken or omitted to be taken in reliance on it, is
> prohibited
> and may be unlawful. When addressed to our clients any opinions or advice
> contained in this email are subject to the terms and conditions expressed
> in
> the governing CyberNET client engagement letter or similar agreements.
> 
> **************************************************************************
> ***
> 
> 
Please visit http://www.ipswitch.com/support/mailing-lists.html 
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
>Ws���+a���0S>0S�!r?���i��(tm)��Sx%S�l?٥�?ޭ騽�_�?�?+%S�@oe
�?+ޡ�aS�b�جj��*��y�a���0(tm)��j�!S�oe�o�(tm)��~S�>�%S�b��"��\
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.

An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/

Reply via email to