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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Connectivity depending on ping

Status
Not open for further replies.

TaylorDavidI

Technical User
Apr 20, 2007
36
CA
We are having an interesting issue in our office. We use two gateways on the same segment depending on what department the computer is meant for; one is a Windows Server 2003 system running routing and remote access. The other is a RouteFinder network appliance.

When trying to connect to the web interface on one of our servers using the RouteFinder as the gateway we aren't able to open the page either by DNS name or IP address. If we send a ping to the server we get responses and then are able to connect but after about 20 minutes the connection drops and we must ping again.

If we set the default gateway of the systems to our windows server there are no connection problems. The odd thing about this is that server only has one NIC installed and just routes most traffic to the RouteFinder.

The server is on a separate subnet within the building and both of the gateways we use route traffic to it in the same manner. Can anyone give me an idea of where else to look for my answers?

David I. Taylor
A+, Network+, MCP Windows XP
 
Possible reasons:

1. Wrong configuration on RouteFinder
2. RouteFinder needs restart / reset because of some internal bug.
3. Wrong routing information entered on the Target Web Server. (it is capable to return the packet through RouteFinder - Windows Gataway path only)




Victor K (Microsoft Consulting Services)
MCSA/MCSE:Security & Messaging;CNE;CCSE+;CIWSP;CIWSA;Network+;Security+;CCNA;nCSE;CISSP
 
I've checked the RouteFinder and all of the configuration appears the same as on the Windows server as far as routing goes. There are no packet filtering rules associated with the subnets involved and all other traffic appears unaffected.

I can see about having the router restarted tonight after hours but I won't have a response on the results until tomorrow morning.

The target server is not running any routing services, just IIS. Everything in IIS seems to be set up properly; all computers are allowed access and anonymous logins are allowed over the web.

Also there are no IP restrictions in place for access and the windows firewall is off.

David I. Taylor
A+, Network+, MCP Windows XP
 
Interesting ... it more and more looks like a bug. I had similar issue with ISA server (exactly that "ping" issue as you have). That ISA was installed in a Virtual Environment and it seems that it was the reason for such behavior. When I moved it out to physical PC - all became fine.



Victor K (Microsoft Consulting Services)
MCSA/MCSE:Security & Messaging;CNE;CCSE+;CIWSP;CIWSA;Network+;Security+;CCNA;nCSE;CISSP
 
It seems that the RouteFinder's firmware is not up to date. We're going to try updating it and see what happens.

David I. Taylor
A+, Network+, MCP Windows XP
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top