September 2, 2008 at 5:01 am
Hello there,
I am having a serious problem connecting to a remote SQL Server on the Internet(from my Webhost).
I am having an issue connecting to my Web Host SQL Server. I have listed all the symptoms of the failure and having worked on this problem for the best part of 3 months and I have finally come to the conclusion that I might have to ask for help.
Please I really need help on this issue, I will be very grateful
So here are the symptoms as recommended :
1. What is the connection string in your app or DSN? Don't know, I am using Enterprise Manager
2. If client fails to connect, what is the client error messages? SQL Server does not exist or Access Denied
3. Is the client remote or local to the SQL server machine? Remote
4. Can you ping your server? Yes
5. Can you telnet to your SQL Server? No
6. What is your client database provider? what is your client application? Enterprise Manager/Query Analyzer
7. Is your client computer in the same domain as the Server computer? Different Domains across Internet
8. What protocol the client enabled? TCP/IP
9. Do you have aliases configured that match the server name portion of your connection string?I have created an Alias to match the name and IP address.
10. Do you select force encryption on server and/or client? Don't know how this is done
8.
[2a] Tool Used to Connect
What tool or Application are you using to connect to SQL Server? SQL Server 2000 Enterprise Edition SP4 without MSDE SP4 patch installed.
[3] Platform:
1. What is the OS version? Windows 2003 Enterprise Edition
2. Do you have third party antivirus, anti-spareware software installed? Symantec Corporate Edition v 10
September 2, 2008 at 5:31 am
Is the port that SQL Server communicates on open to the internet? If that is the way that you are connecting then that will have to be opened up to the outside world. Typically this is 1433.
With that being said, I highly recommend against doing this without a whole lot of thought and planning to see what would be the proper way to allow access to your database server that is at another site, i.e. VPN or establishing a Point-To-Point network connection layer. When you open the SQL port to the internet you are asking for problems so, you really need to consider what you are doing. Talk with a good network architect so that there can be proper coverage for that server and proper placement in the network topology so that your data and server is not placed at risk.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
September 2, 2008 at 7:04 am
I know the setup is terribly insecure but I am also aware that I have a deadline to show that the SQL Server in my office can communicate with another SQL Server over the internet as I will need to configure replication between two sites.
I intend on redesigning the entire topology after I have initially connected to the remote server.
So yes I do appreciate its insecure but this is an initial setup not a permanent one.
So can you help with the problems I discussed with the Opening post?
Everything seems to be working fine but I think the DNS is to blame but netstat says that a SYN_SENT packet is sent to the Wbhost IP but the SYN_SENT packet is never acknowledged.
Thanks for the advice none the less.
September 2, 2008 at 10:13 am
Back with a couple of questions then, is the port open that SQL Server is communicating on open to the internet? Typically by default it is closed.
Are you specifying the port in your connection from Enterprise Manager? You should be doing something like IP,Port in order to connect to the remote server unless you have properly configured a client side alias. If so, verify that is how your alias is configured.
Being that you are able to ping the server, the above questions should point you to the solution. Thanks for being patient.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
September 2, 2008 at 12:30 pm
Hi there,
Thanks for getting back to me!
I was under the impression that the client machine did not have to have ports open to connect to another(remote) SQL Server. Was i wrong?
I thought that the Server which was accepting connections was the one that needed to open its ports to the Internet?
Another issue that I think could affect this could be that I have an iDirect router/gateway sitting in between our inhouse servers and the internet but after speaking to our ISP they say they have not blocked any ports on the router.
I know that an external connection is started cos netstat clearly states that a SYN_SENT packet is sent to the IP Address but is never acknowledged.
My only guess is that the packet never gets there or is dropped by their firewall.
And btw, do u have any friends good with this sort of thing? Any (and now I mean Any!) sort of help would be desirable!
Thanks a lot
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply