symantec firewall

Hello I have a client that has a symantec firewall. They have websites, and web access for exchange hoste don the inside of there network. Everything works fine on teh inside. But all of a sudden no one on in teh world can hit the websites. I looked at the firewall and it all looks good. I am really stuck any help out there?
eberhardt2329Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
herbusConnect With a Mentor Commented:
Just one quick point, you say dns resolves to the external ip of the firewall,.. was this not the case previously..?  I would've thought this would be normal behaviour if you've got internal servers "published" to be accessible from outside...

Do the firewall logs show any attempted connections (and reasons for failure)..?

"All of a sudden it stopped working" normally (of course, not always) means that something somewhere was changed... who has the ability to mess with the firewall rules/config, and is it absolutely 100% that nobody did anything..?
0
 
mattisflonesCommented:
A tought.. Do they have static or dynamic public IP?
0
 
eberhardt2329Author Commented:
static do you have anyideas i cant go to bed untill I fix this. Thank you so much for responding
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
mattisflonesCommented:
Can you try pinging from outside? Do you get a reply at all? Do the DNS lookups match? (Did they pay the bill to the host of the DNS records?)
Its too litle info to go on so far.. Just toughts..
0
 
eberhardt2329Author Commented:
man I am so stuck right now I will tell you what you needif you can help. If I ping the address of teh website it resolves to teh static external ip of the firewall.
0
 
mattisflonesCommented:
Well, i dont touch symantech products for a good reason.. Theres allways trouble! So i`m not the best man for your troubles..

What you tell me so far is a "clear" indication to some kind of error in the forwarding from the firewall to the webserver...
There is two issues that can be present that comes to mind.
#1: The firewalls settings have been corrupted.
#2: Some setting at the server do not allow connections. (If IIS it can be lack of host headers or port errors.)

I would guess that a check of the FW settings, and a check of the webserver would be a issuesolver.. But i can not be sure..

Maybe someone else will be able to help further, but this is a kind of dead time here at EE.. So it might take a while.
0
 
chouprouteCommented:
Did the settings on Firewall allow to connect to the server? Did it redirect to the server(Internal Address and Port address)?
0
 
herbusCommented:
Glad to hear you got it sorted,.. what ended up being the issue?  Server publishing not enabled or doing it's job properly on the firewall/gateway? Someone had actually changed something? ...or something..? :D
0
All Courses

From novice to tech pro — start learning today.