Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

strange ip problem

Status
Not open for further replies.

blackrabbit

IS-IT--Management
Aug 22, 2002
204
US
This is very strange and i can't figure it out. We have a firewall that forward ports 80 and 443 to our web server. Every now and then something strange happens, where using a packet sniffer i can see the packets coming from my home pc to the server and back to my home pc but the web pages fails to load. If i change the nic ip on the server and change it back to the original ip or change the nic ip and change the firewall to forward to the new ip it starts working fine again for about a week and then it stops working again. Anyone else seen this? Its really aggrevating. Our email server uses the same firewall and nothing strange happens on that server. Its irritating because it basically shuts down our website from the outside until i change the ip of the server's nic.
 
Is this a DNS thing? Do you have any rules or services setup for the webserver on the firewall.
Can you see the web page from inside the perimeter?
 
We have two nics on this server, one for our internal network and one for the outside that has ports 80 and 443 forwarded to it. This issue only effects the nic for the outside connection. When i get a call that the web page is not working form the outside it will still be working from the inside. The only things on the firewall are that ports 80 and 443 are forwarded to the webserver. Not sure if it would be a dns issue.
 
On which interface of the server do you have the default gateway set? It should be set on the outside interface. There should be no gateway set on the inside interface. For any additional subnets inside your network you will need to set permanent static routes.

Realistically, you have a huge security hole by placing your server on both the DMZ and the inside network. If someone takes over the box, they also have access to your inside network. You might as well dump the DMZ and allow ports 80 and 443 directly to your web box on the inside network. That would probably get rid of this problem.

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top