asked on

ForeFront Theat Management Gateway 2010 - Unable to ping external IP address of local host external ip address.

I've believe I've done everything necessary to allow my any pc to ping the external interface on the external host but I seems to have an issue.

My server has 4 nics.
NIC1: Internal Clients 192.168.1.x
NIC2: Perimeter Clients 192.168.2.x (our wireless clients)
NIC3: External 165.138.134.x (Internet using our T1)
NIC4: Insight Internet Provider (Internet using Broad Band, mainly for wireless clients)

I've setup dual host ISP's and that seems to be working just fine.

When I ping each of the server's nic's I get a response back from all of them but the 165.138.134.1 ip address. I've bound 165.138.134.2 to the server and I can ping that address just fine but not the .1 ip address.

I've setup ICMP (Ping) under Remote Management and ICMP under Diagnostic Services to allow from all networks(and local host). I intend to turn that off after I verified that everything is working as expected.

Any ideas? I've already setup an access rule for ping to be allowed from and to all networks(including local host).

p.s. I setup a log to monitor my pc and all my traffic is showing up except when I ping the 165.138.134.1 address. Nothing at all is showing up.

ASKER CERTIFIED SOLUTION

Greg Besso

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

CubeRoot

ASKER

I only wanted to allow it so I could see that everything is working right. I plan on turning off the ping after I know all the routing is working fine. I've messed with this for a day now and at some point it started working a little differently. I'm now able to ping the external address from the Internet but not from an Internal client. I'm swamped with administrative stuff at the moment. I'll do a full test of what is and isn't working later today and post an update.

p.s. I fear is I have a routing issue, like the return ping is being misdirected.

SOLUTION

simonlimon

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

CubeRoot

ASKER

I was on vacation for a week. I've done some research and here's my problem. I originally had a window 2000 server with isa 2006 loaded and everything worked just fine. I'm upgraded to Windows 2008 Enterprise Edition w/ Threat Management Gateway. Everything works pretty much as expected but I do have an annoying problem. It's annoying because I don't know why and I have some hard coded dns entries on a few machines in the building that I will need to change or fix this issue. I've went over my rules and to my best ability everything looks good but here's what's happening.

Firewall Nics
192.168.1.254 Internal Network
192.168.2.254 Perimeter Network (Wireless)
165.138.134.1 External (Load balancing ISP's)
74.143.90.220 External

The Internal network has an Internal DNS Server and a DHCP Server and works as expected.
The Public wireless (Perimeter) has an DHCP Server working on the Perimeter network which directs clients to the external DNS Server (The one that the rest of the world sees) which runs on the firewall's external IP address 165.1381.134.1 & 165.138.134.2.

165.138.134.2 is working and responds to clients. 165.138.134.1 ignores all requets.

I used a pc on the internal network to ping 65.138.134.1 while logging all events for that client and nothing shows up on log.
When I ping 165.138.134.2 or 165.138.134.254(router) I get the ping results but still nothing shows up in the logs.
If I ping www.google.com I get results.

I'm thinking it's something related to the external subnet. I'm not sure where to go from here.

CubeRoot

ASKER

The more I play with this, the more I think it just won't let me publish anything to 165.138.134.1 but to any other address is just fine.

Greg Besso

Back to your original concern. Pinging is not going to tell you that everything is working properly. It's just going to expose your server in a way you don't need to expose it.

If you are publishing services, try telnet to the public IP and port you are trying to publish.
Or just try accessing the services you are publishing.

CubeRoot

ASKER

This problem still exists but I must admit that I've moved on to more pressing issues. I'm considering that I might have a routing issue but nothing is standing out specifically.

SOLUTION

Greg Besso

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

CubeRoot

ASKER

I have of course a dozen or so published services, ranging from dns, email to websites. If have set the External listener to listen on 165.138.134.1 and 165.138.134.2. If I try using any of the published services on 165.138.134.1 I get no reply at all. If I try 165.138.134.2 then it works fine.

Both IP's are bound to the FTMG.

CubeRoot

ASKER

I may revisit this issue in the future. At the moment I'm just not posting anything on the primary external ip address. If someone wants to clean this up, that's fine.

CubeRoot

ASKER

Somewhere long the way this problem cleared itself up. I don't remember doing anything that would fix the issue but I retested the problem and it appears to be gone. Don't you love problems like this..I have no idea if the problem will return or not.

CubeRoot

ASKER

Thank you for your comments on this problem. Since the issue cleared itself up, there's no way to continue diagnosing the problem. Thank you for your efforts.