[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?

http is not working on our network only https works

Posted on 2017-10-13
3
Low Priority
?
37 Views
Last Modified: 2017-10-16
We have 120 users on network with cyberoam ( 50 ING ) firewall  configured , from last 2 weeks we had issues like http websites not resolving getting error could not reach . But on other ISP it works fine.

Environment :
Cyberoam 50 ING Firewall with BSNL ISP configured  ....connected to Unmanaged switches
Internal AD integrated with DNS Server windows 2012 r2
All server + clients having primary dns server is windows server local IP address

But if do the nslookup domain name then it resolves fine but on browser it stucks. But sometime it works fine too.

ipconfig / flushdns
ipconfig / release
ipconfig / renew
ipconfig / registerdns
Winsock reset
Antivirus scan + malware scan , after malware scan it works for sometime and again it stucks. some of PC having the malware or spyware which blocks the http 80

everything did but http is not working . Only remains the Cyberoam Firewall firmware upgrade and restart of Windows 2012 server.

Please assist me to resolve this issue on urgent basis

Regards,
Vijay Kadadi
0
Comment
Question by:kadadi_v
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 14

Expert Comment

by:Andy M
I would start by checking firewall logs - see if there's anything there indicating a block on port 80. Worth checking your outgoing tcp firewall rule to ensure port 80 is still enabled and allowed.

You could also run wireshark to see what's happening to the port 80 requests.

To rule out DNS issues (though your nslookup works so I don't believe this would be the case) set static dns on one of the affected machines to use something like google (8.8.8.8, 8.8.4.4) or opendns (208.67.222.222, 208.67.220.220).
1
 
LVL 31

Expert Comment

by:masnrock
What do your filtering policies look like on the Cyberoam?
0
 
LVL 5

Expert Comment

by:William Miller
If this is specifically on HTTP (Port 80), this sounds like a filtering issue. Like the other two experts here have alluded to, you'll want to check the hardware firewall to make sure Port 80 isn't being blocked. It's a common practice to keep people off of sites considered insecure. It's just another step some companies will take to steer their employees away from going to places they're not supposed to go.
1

Featured Post

Plesk WordPress Toolkit

Plesk's WordPress Toolkit allows server administrators, resellers and customers to manage their WordPress instances, enabling a variety of development workflows for WordPress admins of all skill levels, from beginners to pros.

See why 2/3 of Plesk servers use it.

Join & Write a Comment

Originally, this post was published on Monitis Blog, you can check it here . It goes without saying that technology has transformed society and the very nature of how we live, work, and communicate in ways that would’ve been incomprehensible 5 ye…
In the absence of a fully-fledged GPO Management product like AGPM, the script in this article will provide you with a simple way to watch the domain (or a select OU) for GPOs changes and automatically take backups when policies are added, removed o…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

649 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question