Re: [IUG] Firewall and III problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Mon, 05 Apr 2010 15:16:18 -0400
- From: "Judith A Schneider" <SchneiderJ at gao dot gov>
- Subject: Re: [IUG] Firewall and III problems
Doesn't everything that goes out through your firewall pick up the IP from the firewall? We have a really strict, tight firewall, and all of our services that are based on IP recognition use the IP from the firewall, not the internal server.
Can't answer the NAT question, don' know nuthin' 'bout that. 8)
Hope this isn't a really stupid question. 8)
--
Judy Schneider
US GAO Library
schneiderj at gao dot gov
(202) 512-4304
My opinions are mine! All Mine!
So many books .... So little time
On 4/5/2010 at 1:32 PM, Lindsay McVey <lmcvey at wscc dot edu> wrote:
> Hi,
> I've looked through the archives and I can't really find anything that
> address my problem so I wondered if I could ask for advice?
> We have recently moved our III server from an external IP to an internal
> 10.10.x.x IP and brought it inside the firewall. Prior to this, our server
> was located on an external IP outside of the firewall. And it worked fine.
> :)
> We worked with III and changed the IP, moved it inside, and we're using NAT
> to send it out through an external IP. Inbound traffic is coming in on our
> external ip 205.x.x.x and is translated to the internal 10.10.x.x just fine.
> But, here is the problem. For some reason, all outbound traffic gets
> translated up to our firewall external IP and *not* the external IP we've
> set up with NAT. We've seemingly tried everything. We've even assigned the
> server it's own port on our firewall. We are about two steps away from
> throwing it back outside... but I wanted to see if anyone else has any
> experience with this. Sonicwall is our firewall. Standard one-to-one NAT
> from and external to an internal IP.
> Thanks in advance. Email me off list if you'd prefer.
> Lindsay
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.