lan SQL connection problem with new router

[opticalman]

I have 8 computers on a LAN using XP home connecting to SQL EXPRESS 2005 on a machine using XP Pro. The setup has worked for over 5 years. A router plugs into the 24 port Dell switch. The router is to allow internet access.

We need to set up a VPN and installed a new router. Once the router is installed, I cannot connect to the SQL EXPRESS. I can ping the SQL host, but the SQL connection is lost.

Here are some unnusual clues, that may be of no importance.

If the router is not connected to the cable modem, I can connect to SQL. Once the router is connected to the cable modem, the SQL connection is lost.

When the router is first installed, everthing works. I can reach the internet. I can connect with SQL. But after rebooting the computer, I can no longer connect with SQL.

Three routers have caused the same symptom. I am back to using our old router (Web Ramp 700) until a solution is found.

 

[biglebowski]

can you telnet using port 1433?

telnet "SQL IP ADDRESS" 1433

if not it's your router blocking the sql port, have a look at the router docs to see if it has options for port forwarding or how to open ports on it.

Biglebowskis Razor - with all things being equal if you still can't find the answer have a shave and go down the pub.

 

[opticalman]

@biglebowski

Thanks you for your suggestion. With the old router that works,
per your suggestion, I did 'telnet "SQL IP ADDRESS" 1433 '
I recieved the error message "could not open the connection to the host........"


Should I expect something else with the router that does not work?

 

[biglebowski]

it's just to identify if your router is blocking the port. Looks like you need to open up port 1433 for it to work, what is the make/model ofthe router?

Biglebowskis Razor - with all things being equal if you still can't find the answer have a shave and go down the pub.

 

[opticalman]

I have found a solution, though I admit I did not find the problem.

The clients on our LAN were connecting to the host via ODBC using TCP/IP. I changed the ODBC CLIENT CONFIGURATION from TCP/IP to OPEN PIPES. It now works as desired.

I consider this question resolved.