Linked SQL Server and Windows 2003 Firewall/SCWQL

SQL Experts,
1. I have two Windows 2003 Standard Server boxes.
2. Both host MS/SQL Server Standard 2000.
3. Server#2 is linked to Server#1 using SQL/Enterprised Link Server applet.
4. Both servers have Win2k3 Service Pack#1 installed.
5. Both server enable firewall via SCW (Security Config. Wizard). I locked
everything but SQL Server Port (1433).
6. Both use TCP/IP as top (default) network protocol.
7. All Windows XP clients can read/write to and from the two SQL servers
without problem (Windows and SQL Auth. are used).
Problem: Server #2 cannot read data from Server#1 it links to. It said
Sever#1 is not running or access denied. Even if SQL Ports on both boxes are
widely openned. because clients from outside can get to it. Hopwever, if I
disable firewall on Server# 1, then Server# 2 will be able to read data from
#1. I really like the FW in service pack# 1. But if I have to disable it in
order to use "Link Server" (server-to-server) in MS/SQL then this new thing
(FW) in W2k3 is really useless ! Therefore I assume that I am missing
something very important ?
Thanks
JohnI suspect it's the way you have your firewall setup, check the following:
INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/kb/287932/
Steve
"WJ" <JohnWebbs@.HotMail.Com> wrote in message
news:udrXXC%23OFHA.2252@.TK2MSFTNGP15.phx.gbl...
> SQL Experts,
> 1. I have two Windows 2003 Standard Server boxes.
> 2. Both host MS/SQL Server Standard 2000.
> 3. Server#2 is linked to Server#1 using SQL/Enterprised Link Server
applet.
> 4. Both servers have Win2k3 Service Pack#1 installed.
> 5. Both server enable firewall via SCW (Security Config. Wizard). I locked
> everything but SQL Server Port (1433).
> 6. Both use TCP/IP as top (default) network protocol.
> 7. All Windows XP clients can read/write to and from the two SQL servers
> without problem (Windows and SQL Auth. are used).
> Problem: Server #2 cannot read data from Server#1 it links to. It said
> Sever#1 is not running or access denied. Even if SQL Ports on both boxes
are
> widely openned. because clients from outside can get to it. Hopwever, if I
> disable firewall on Server# 1, then Server# 2 will be able to read data
from
> #1. I really like the FW in service pack# 1. But if I have to disable it
in
> order to use "Link Server" (server-to-server) in MS/SQL then this new
thing
> (FW) in W2k3 is really useless ! Therefore I assume that I am missing
> something very important ?
> Thanks
> John
>|||Dear John,
Did you solve your linked server problem ? Now , i am suffer the same
problem. Do you got any solution ?
Thanks a lot
From Agnes
*** Sent via Developersdex http://www.codecomments.com ***

Linked SQL Server and Windows 2003 Firewall/SCWQL

SQL Experts,
1. I have two Windows 2003 Standard Server boxes.
2. Both host MS/SQL Server Standard 2000.
3. Server#2 is linked to Server#1 using SQL/Enterprised Link Server applet.
4. Both servers have Win2k3 Service Pack#1 installed.
5. Both server enable firewall via SCW (Security Config. Wizard). I locked
everything but SQL Server Port (1433).
6. Both use TCP/IP as top (default) network protocol.
7. All Windows XP clients can read/write to and from the two SQL servers
without problem (Windows and SQL Auth. are used).
Problem: Server #2 cannot read data from Server#1 it links to. It said
Sever#1 is not running or access denied. Even if SQL Ports on both boxes are
widely openned. because clients from outside can get to it. Hopwever, if I
disable firewall on Server# 1, then Server# 2 will be able to read data from
#1. I really like the FW in service pack# 1. But if I have to disable it in
order to use "Link Server" (server-to-server) in MS/SQL then this new thing
(FW) in W2k3 is really useless ! Therefore I assume that I am missing
something very important ?
Thanks
John
I suspect it's the way you have your firewall setup, check the following:
INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/kb/287932/
Steve
"WJ" <JohnWebbs@.HotMail.Com> wrote in message
news:udrXXC%23OFHA.2252@.TK2MSFTNGP15.phx.gbl...
> SQL Experts,
> 1. I have two Windows 2003 Standard Server boxes.
> 2. Both host MS/SQL Server Standard 2000.
> 3. Server#2 is linked to Server#1 using SQL/Enterprised Link Server
applet.
> 4. Both servers have Win2k3 Service Pack#1 installed.
> 5. Both server enable firewall via SCW (Security Config. Wizard). I locked
> everything but SQL Server Port (1433).
> 6. Both use TCP/IP as top (default) network protocol.
> 7. All Windows XP clients can read/write to and from the two SQL servers
> without problem (Windows and SQL Auth. are used).
> Problem: Server #2 cannot read data from Server#1 it links to. It said
> Sever#1 is not running or access denied. Even if SQL Ports on both boxes
are
> widely openned. because clients from outside can get to it. Hopwever, if I
> disable firewall on Server# 1, then Server# 2 will be able to read data
from
> #1. I really like the FW in service pack# 1. But if I have to disable it
in
> order to use "Link Server" (server-to-server) in MS/SQL then this new
thing
> (FW) in W2k3 is really useless ! Therefore I assume that I am missing
> something very important ?
> Thanks
> John
>
|||Dear John,
Did you solve your linked server problem ? Now , i am suffer the same
problem. Do you got any solution ?
Thanks a lot
From Agnes
*** Sent via Developersdex http://www.codecomments.com ***

servers

I have to link servers using sql server 2000 standard edition...
for anyone who has done this.... upon linking the servers using the other options radio button choice... is it suppose to show all the databases for that server under the drop down...
its only showing tables and views... which i get an error 7339 or error 17:

can anyone assist...or lead me in the right direction....
thanks,
jonathanhttp://support.microsoft.com/kb/814398
http://support.microsoft.com/default.aspx/kb/241267
If you google on error 7399 you would get relevant forum posts too.|||I resolved the issue|||How ?|||permissions on the standy server did not match or map to the prod box.....
under the security tab i changed the option being made using this security context to begin made using the login's current security context|||ahhhh...yes.

The ole' security issue...