Log Shipping accross the WAN?

Can I setup Log Shipping accross the WAN if I enable very specific firewall
rules to allow access to MSSQL. (ie. WAN IP on port 1440 to WAN IP2 on 1440)
Has anyone tried this? Is it as simple as opening up that port, or are there
a whole host of ports to open up.Hi
Log shipping relies on a file copy from one server to another, so you need
the NT Challenge Response ports (135, 137, 138, 139) and 445. Then you need
to port that SQL Server listens on, which is generally 1433, depending on
your installation.
Look at http://www.speedguide.net/ports.php to see what ports I list and if
it is UDP or TCP.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Soul_Chicken" <Soul_Chicken@.discussions.microsoft.com> wrote in message
news:DC13165D-15E8-4A71-99BC-DA2B9AC4AE9C@.microsoft.com...
> Can I setup Log Shipping accross the WAN if I enable very specific
> firewall
> rules to allow access to MSSQL. (ie. WAN IP on port 1440 to WAN IP2 on
> 1440)
> Has anyone tried this? Is it as simple as opening up that port, or are
> there
> a whole host of ports to open up.
>|||In article <#4rPey6kFHA.1996@.TK2MSFTNGP10.phx.gbl>, mike@.epprecht.net
says...
> Hi
> Log shipping relies on a file copy from one server to another, so you need
> the NT Challenge Response ports (135, 137, 138, 139) and 445. Then you need
> to port that SQL Server listens on, which is generally 1433, depending on
> your installation.
> Look at http://www.speedguide.net/ports.php to see what ports I list and if
> it is UDP or TCP.
Connections between SQL Servers in different locations (WAN to WAN)
should be done through a VPN tunnel and not exposed directly to the
Internet - there is no reason to expose a SQL server to the Internet.
--
spam999free@.rrohio.com
remove 999 in order to email me