Re: Unable to browse for available SQL servers across subnets??
From: Steve Thompson (stevethompson_at_nomail.please)
Date: 06/23/04
- Previous message: Peter: "When will port 445 be used by SQL Server?"
- In reply to: dude: "Unable to browse for available SQL servers across subnets??"
- Next in thread: Jasper Smith: "Re: Unable to browse for available SQL servers across subnets??"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Jun 2004 15:27:58 -0400
"dude" <dude@aol.com> wrote in message
news:ufegA$TWEHA.1164@tk2msftngp13.phx.gbl...
> I have our DBA complaining that I have changed something on the network.
He
> can only browse for available SQL servers in the subnet where Enterprise
> Manager is installed. I verified that this is indeed the case. He has a
> need to use a SQL database monitoring software to monitor SQL servers that
> span aross at least 2 different subnets. During SQL server registration
in
> Enterprise Manager, I can only browse list of servers on the local subnet.
> Is there any way to change this behavior so I can browse across certain
> subnets? I doubt that SQL has the concept of Master Browsers like WINS
that
> exchange browse lists info across subnets. Manually entering the server
> name during the registration process does work.
>
My first thought is you may have an issue with your browse list. You may
want to try enabling named pipes on the server side to see if the server
name appears.
Another possibility, create an SQL Server Enterprise Manager *.MSC file with
all of the SQL Servers defined, then share this file with the DBA's...
Steve
- Previous message: Peter: "When will port 445 be used by SQL Server?"
- In reply to: dude: "Unable to browse for available SQL servers across subnets??"
- Next in thread: Jasper Smith: "Re: Unable to browse for available SQL servers across subnets??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
