Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server communication over subnets Expand / Collapse
Author
Message
Posted Wednesday, November 14, 2012 2:14 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 6:13 AM
Points: 307, Visits: 475
Hi Folks,

OK, the problem is that I am trying to configure two SQL Server 2005 machines to communiacte over two subnets so obviously a router is sitting in the middle. When I run osql -L there are no SQL Servers in the second subnet listed and so my first thought was that traffic was being blocked at the router. Unfortunately it is not that simple!

I have done the following on both ends of the proposed connection:

1. I have used the Configuration manager to ensure that TCP/IP is enabled

2. In the Surface Area Configuration Manager I have ensured that Remote Conections are allowed.

3. At the instance level in the Server Properties under Connections, "Allow Remote Connections to this Server" has been checked.

I can PING the target router to see that it is alive but SQL Server itself cannot see the other instance.

I would be grateful for any help you can offer!

Regards,

Kev
Post #1384474
Posted Wednesday, November 14, 2012 2:23 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 8:20 PM
Points: 112, Visits: 802
Could it be that SQL Browser services needs to be active so that oSQL will see servers. Also you may want to check if your firewall settings have blocked UDP 1434 since that's used by SQL Browser?


--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully
Post #1384480
Posted Wednesday, November 14, 2012 3:19 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 6:13 AM
Points: 307, Visits: 475
Hi!

Thanks for the prompt answer.

I forgot to mention that! The SQL Server Browser is active on both ends. Does the browser not use 1433 for the default instance and then 1434+ for the remaining named instances?

Regards

Kev
Post #1384503
Posted Wednesday, November 14, 2012 9:28 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Saturday, March 8, 2014 8:00 AM
Points: 24, Visits: 147
The SQL Browser Service uses UDP 1434. This is commonly blocked at firewalls. Why do you need to discover the server using Browser? Can you connect directly to the FQDN or IP Address?
Post #1384728
Posted Wednesday, November 14, 2012 11:20 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 6:13 AM
Points: 307, Visits: 475
The Browser is the most convenient way to connect to each of the servers. Using the "Connect to" dialog box enables our developers and testers to connect to instances and databases without the additional hassle (and some of these people look at it as being "hassle"!) of remembering an IP Address.

The second reason the Browser is helpful for us is the use of the "osql -L" command that allows us to inventory the SQL Server landscape from the command line although at the moment this command cannot cross the boundary between the subnets.

The third reason is that our Reporting and Analysis Services-based servers have the business requirement that they should be accessible using Browser services, a point I have argued but stands firm.

A connection using an IP Address also does not work, something that is more than a little irritating and which also makes me think that perhaps an access list is in place at the network boundary. The problem is that our Infrastructure Team assure me that no firewall exists between the subnets and that router-based ACLs are also not active.

The problem is a confusing me...........
Post #1384980
Posted Thursday, November 15, 2012 12:15 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Saturday, March 8, 2014 8:00 AM
Points: 24, Visits: 147
Can you telnet to the SQL Server port over the router? Don't assume it is 1433. Check using SQL Server Configuration Manager. Beyond this, I would use WireShark to see trafffic to/from the boxes.
Post #1385301
Posted Thursday, November 15, 2012 1:22 PM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 8:20 PM
Points: 112, Visits: 802
Agree with Randy they potentially could be on non default port for your SQL Servers. (e.g. named instance possibly)

Have you tried using a tool to check the ports?

Microsoft has a tool that allows you to specify specific IP address and port.
http://www.microsoft.com/en-us/download/details.aspx?id=17148

Hope that works? Then you can confirm if the port is blocked maybe?




--------------------------------------------------
...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully
Post #1385337
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse