Re: Manage SQL server accross WAN??

From: Ole Kristian Bangås (olekristian.bangas_at_masterminds.no)
Date: 11/25/05


Date: Fri, 25 Nov 2005 07:00:53 -0800


"mostro" <mostro@nospam.com> wrote in
news:f7SdnVXY5ffkzhvenZ2dnUVZ_vydnZ2d@adelphia.com:

> Has anyone had any experience managing a SQL 2000 server behind a a
> locked down router? I have to move a SQL server into a secure DMZ and
> give access to it from an internal netework. If I open TCP port 1433
> and UDP 1434 will this allow SQL management using Enterprise Manager
> installed on the remote client?

I do think you only need TCP 1433 to work with SQL Server, and yes it
should work.

-- 
Ole Kristian Bangås
MCT, MCDBA, MCDST, MCSE:Security, MCSE:Messaging


Relevant Pages

  • Re: Connection Error
    ... Most likely the port 1433 is blocked on this SQL Server by Windows Firewall. ... So try open TCP port 1433 on the SQL Server machine you cannot telnet to. ... but then an error occurred during the login process. ... Shared Memory Provider, error: 0 - No process is on the other end of the ...
    (microsoft.public.sqlserver.security)
  • Re: putting a sql server behind a firewall
    ... that I got it was that sql server was publicly accessable... ... > Server - only IIS is, and it's running on the same physical machine. ... installation of a firewall - software or hardware - will have zero ... You will need to open TCP port 80 for incoming traffic. ...
    (microsoft.public.sqlserver.security)
  • PS name problem
    ... I 've an access 2000 adp connected to an sql server 2005 database. ... The real name, that i can see in sql management, is "Ps_Test ". ... This problem concerns all stocked procedure. ...
    (microsoft.public.access.adp.sqlserver)