Connect to a server in another domain

[Jason]

Machine A in domain A is running SQL 2008. From there I can see my other SQL
Servers in domain B. - great

When I'm on machine B in domain B, I can explore files on machine A

However, when I'm on Machine B I cannot see SQL Server A. I did management
studio 2005->Connect->Network Servers->Browse for more... it only shows me
the servers in domain B. Why is this?

because it's a newer version?
because remote connections are disabled?
because the firewall is blocking it?

On Machine A I've got SQL server and SQL Server browser running

please help

[Erland Sommarskog]

Can you connect to machine B, if you type it in?

I never use the Browse option, and it goes without saying that if you
are on a large corporate domain, you don't want to interview all machines
to see if they have an SQL Server runing on it.

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Rick Byham, MSFT]

Providing the browse information for instances of SQL Server is a service
provided by the SQL Server Browser Service on the computer running SQL
Server. Since you say the SQL Server Browser Service is running on Machine
A, that's a good start.
The Browser uses UDP port 1434. Make sure that UDP port 1434 is open on the
firewall of Machine B.
And UDP (use-datagram protocol) is usually (well at least often) not
propagated through routers. Passing all UDP traffic could clutter up the
network. But that's a router configuration issue which isn't my specialty.
However it would be odd for UDP to be allowed one direction but not the
other, so my guess is that your problem is with the firewall on Machine B.
--
Rick Byham, MSFT
(Implies no warranty or rights)

"Erland Sommarskog" <esq...@sommarskog.se> wrote in message
news:Xns9CE081E03...@127.0.0.1...