Can't ping certain ip through route

  • Thread starter Thread starter knoche
  • Start date Start date
K

knoche

Hello everyone...

I'm trying to setup publishing on my 2 SQL servers for backup purposes.

Main SQL server - (win2k)2 node clustered sql server with ip address of
192.168.0.245

Backup SQL server - (win2k)ip address of 192.168.1.2

I have a VPN connection set up between the two. I also have DFS
running that works fine through the routes.


The routing is working fine. From the backup server, I can ping EVERY
SINGLE IP in the 192.168.0.0/27 range EXCEPT the sql server ip
(192.168.0.245). I can even ping the cluster IP that the SQL service
resides which is .250

From a pc in the 192.168.0.0/27 network, I can connect to .245 fine.
Click to expand...

I'm honestly a bit lost of even where to look for solutions on this.
Any suggestions or ideas would be greatly appreciated


*Note: the clustered sql server is working fine and not the issue (it's
been running the way it is for about 2 yrs now)
 
Ping may be blocked at firewalls or you may
have a real routing or ip problem so the first
step when ping fails (by address) is to TRACERT
or PATHPING (I don't like this one as it is too
slow due to spending a lot of time gathering extra
info that I almost never use.)

tracert WHEREVER

See how far you get...the problem may be right there,
or just beyond, or even on the way back to you but
at least you get a closer idea of the problem location.

If you have routing (ping is blocked but there are still
limited connections) only on specific ports you will
need to either open or test for that....
I'm trying to setup publishing on my 2 SQL servers for backup purposes.
Main SQL server - (win2k)2 node clustered sql server with ip address of
192.168.0.245
Backup SQL server - (win2k)ip address of 192.168.1.2

I have a VPN connection set up between the two. I also have DFS
running that works fine through the routes.
Click to expand...

Interesting. Any port filters?
The routing is working fine. From the backup server, I can ping EVERY
SINGLE IP in the 192.168.0.0/27 range EXCEPT the sql server ip
(192.168.0.245). I can even ping the cluster IP that the SQL service
resides which is .250
Click to expand...

Is it possible the SQL server has disabled Ping responses
with either the Firewall or an add-on firewall or other
filter?
I'm honestly a bit lost of even where to look for solutions on this.
Any suggestions or ideas would be greatly appreciated
Click to expand...

If running on Win2003 (or XP) I would strongly suspect the
new built-in firewall.

If running on Win2000 (this newsgroup) I would strongly
suscect any ADD-ON firewall (Symantic, Outpost, etc.)

For both, I would look to filtering firewalls or routers between
the two.
*Note: the clustered sql server is working fine and not the issue (it's
been running the way it is for about 2 yrs now)
Click to expand...

I don't know the specific ports you are needing but you can
use Telnet to test if it is TCP, or NetCat (nc.exe download
by searching Google) if it is EITHER TCP or UDP.

telnet WHEREVER PORTNUMBER
(portnumber is TCP only, won't work for UDP)

If you get ANY kind of connection (even a blank screen or
gargage) then you probably connected and the problem is
not likely due to filtering/firewalls but is authentication or
something else.
 
Back
Top