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...........