Unable to connect through routed network

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

knoche - 28 Jan 2005 14:29 GMT

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.

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)

Reply to this Message

Steven S. Warren - 29 Jan 2005 01:35 GMT

Interesting problem. Let me throw some things out there for you.

Are your default gateways correct on the SQL Server and Backup Server. This
can cause routing problems.

When you do a tracert from the command prompt, to the 192.168.0.245 (SQL
Server), where is it failing.

When you do an ipconfig /all does it list all the ip addresses such as the
virtual ip, and the local ip?

Can you ping the 192.168.0.245 (sql server) and get a reply on the machine
itself?

On your VPN connection, did you configure your DHCP relay properly?

This should help get you started in the right direction. It is really
strange why you cant ping the server.

> Hello everyone...
>
[quoted text clipped - 20 lines]
> *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)

Reply to this Message