at a client. I would like to be able to connect my SQL Enterprise
manager in case I need to do something in their database and I need to
do it remotely. I have the MSDE set to mixed mode authentication and
opened the ports (1433 and tried 2433 as well because client network
utility said it used that port) but I cannot connect for some reason.
Any clues what I still need to do?
The other question is: is it safe to connect a SQL server directly to
the net? The SQL Server is fully up to date with the latest patches.
Are there any guidelines that I need to follow when I want to do this
(in a safe way)?
Thanks in advance,
Stijn Verrept.You should consider establishing a VPN connection from your remote client.
Then use Terminal Server or Remote Desktop to administer the server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] wrote:
quote:
> You should consider establishing a VPN connection from your remote
> client. Then use Terminal Server or Remote Desktop to administer the
> server.
Thanks for your answer Kevin. I can login with TS but MSDE does not
include enterprise manager so I cannot install this on the clients pc!
Kind regards,
Stijn Verrept.|||So, unless the client as a Terminal Server that you can install the SQL
Client tools, your options are limited.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] wrote:
quote:
> So, unless the client as a Terminal Server that you can install the
> SQL Client tools, your options are limited.
What do you mean? The client is running a terminal server. And I can
log in on that machine. The problem is that it does not have
Enterprise manager. This is why I need to connect with my enterprise
manager to the terminal server through the net. Isn't this possible?
Why doesn't it want to work?
Kind regards,
Stijn Verrept.|||Here's what I'm recommending:
1. Client -->VPN -->Terminal Server (with Enterprise Manager Installed)
-->MSDE
or
2. Client (with Enterprise Manager) -->VPN -->MSDE
Option 1 would be preferred.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Im having exactly the same problem.
However, we need access to both our SQL Server and their Server as we
do database design work as part of our web development and need to
upload databases we have created.
Weve tried the VPN route, but our policy is to keep our SQL Server
well behind the firewall, and there are no exceptions (Clients company
information kept on them so security is a big deal) so they cant see
our DB.
They have opened all ports for our IP address so all traffic is
allowed, but we can still not connect to their DB.
A simple yes or no is required, Can you connect to a remote MSDE
Server across the internet and register it in SQL Server Enterprise
manager?
TCPIP and Named Pipes are Installed and enabled on MSDE
kevmc@.online.microsoft.com (Kevin McDonnell [MSFT]) wrote in message news:<v40lyXs2DHA.3564@.cp
msftngxa07.phx.gbl>...
> Here's what I'm recommending:
> 1. Client -->VPN -->Terminal Server (with Enterprise Manager Installed)
> -->MSDE
> or
> 2. Client (with Enterprise Manager) -->VPN -->MSDE
> Option 1 would be preferred.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.|||Can you connect to a remote MSDE
Server across the internet and register it in SQL Server Enterprise
manager?
Simple Answer:
Yes. Over TCP. As long as the ports are open on the firewall.
287932 INF: TCP Ports Needed for Communication to SQL Server Through a
Firewall
http://support.microsoft.com/?id=287932
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Kevin, Thats what I thought, but not what I wanted to hear!
This means we have a different problem which is going to be a nightmare
to sort out.
If SQL Server (MSDE) has the TCPIP netlib enabled and the default port
is being used (1433), do we need to have 1433 enabled on both firewalls
(theirs and ours) to enable enterprise manager to register this server?
Also, Do we need to open port 1434 (Ive heard that this is needed for 2
way communication)
Any other ideas why I can connect to our ISP hosted SQL Servers, but not
our clients (who hosts their own website) even though they have tried
with the server outside the firewall? Even If I make a vpn connection to
the SQL Server box, and can ping it by name, I still cant connect. I get
the error:
SQL Server does not exist or access is denied
ConnectionOpen(Connect())
Desperate to get this sorted now
Thanx again
remove 'REMOVESPAM.' for email
Karl Rhodes
Internet Solutions Architect
The Learning Business & Keywave
www.thelearningbiz.com
www.keywave.com
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||from previous post:
"This means we have a different problem which is going to be a nightmare
to sort out.
If SQL Server (MSDE) has the TCPIP netlib enabled and the default port
is being used (1433), do we need to have 1433 enabled on both firewalls
(theirs and ours) to enable enterprise manager to register this server?
Also, Do we need to open port 1434 (Ive heard that this is needed for 2
way communication)"
You would need 1433 open on the remote firewall. You client would open up
a tcp session to 1433 and communicate back to your
client on a random tcp port.
Ex. client opens port 2000 and sends traffic to the remote MSDE on 1433
The communication comes back from 1433 to your client port 2000.
"Any other ideas why I can connect to our ISP hosted SQL Servers, but not
our clients (who hosts their own website) even though they have tried
with the server outside the firewall? Even If I make a vpn connection to
the SQL Server box, and can ping it by name, I still cant connect. I get
the error:
SQL Server does not exist or access is denied
ConnectionOpen(Connect())
"
This error is meaningless without the OS error number.
Force a TCP sockets connection with ISQL.exe
Ex. ISQL -Stcp:ServerName -Uuserid -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sql
No comments:
Post a Comment