Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 Import/Export (DTS) and Replication (2000)
 MS SQL Replication error!

Author  Topic 

kanirip
Starting Member

12 Posts

Posted - 2008-02-07 : 13:27:41
Please I need some one in the house that is knowledgable about SQL Server replication from
an in-house SQL Server database to an online, web based database.

Right now I'm hitting a brick wall because anytime I try and connect to the online SQL Server
I get an 'SQL Server not found or Access is denied' error.

I have been at my wits end trying to solve this error!

I have tried monitoring the active network connections using netstat and it does send packets to the web host server IP address but it seems that the web host server never ACKnowledges the packet.

I have disabled my firewall!

But I can ping the server.

I have tried using SQL Enterprise Manager, Query anayzer, ODBC Connectivity and telnet to try and
connect to that machine all to no avail.

So please anyone with some experience in this, can you give me a hand!

If you are aware of any other means of replicating databases over the internet, i'm quite open to this.


Thanks in Advance!

PS:
Please I have searched through the forums and found no working solutions. If you have any links, don't hesitate to post them here I will give anything a try at the moment!

When you looks into an abyss, the abyss looks also into you-- Friedrich Nietsczhe

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-02-07 : 22:01:02
Hosting company has firewall also.
Go to Top of Page

kanirip
Starting Member

12 Posts

Posted - 2008-02-11 : 09:52:38
Thanks for the reply rmiao!

No they don't! I have contacted them and they say that other people can connect to their
SQL Servers.

Do you think the error is caused by my local SQL Server not being patched with any of the Service Packs?

Thanks a lot!

When you looks into an abyss, the abyss looks also into you-- Friedrich Nietsczhe
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-02-11 : 23:09:35
If you know sql port number, can try telnet to their ip address and port number.
Go to Top of Page

kanirip
Starting Member

12 Posts

Posted - 2008-02-19 : 10:13:39
I have tried this but Telnet can't connect to that port.

What do you think could be te problem? Could it be the ISP is setting up a firewall?

I have tried using MySQL application as a client to their MySQL Server and that works fine.

Thanks rmiao.

When you looks into an abyss, the abyss looks also into you-- Friedrich Nietsczhe
Go to Top of Page

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2008-02-19 : 23:19:13
That means the port is blocked on isp.
Go to Top of Page

kanirip
Starting Member

12 Posts

Posted - 2008-09-01 : 12:16:15
I am sorry but I have to bring this topic back to life because I have recently convinced my organisation to purchase some (quite expensive) public IP addresses so as to address the issue I highlighted in this thread.

But I am still hitting a brick wall.

The ISP (efree2net.com) insist that they have done all they can and they have not blocked any ports on their firewall. And they also state that I am the only one who has problems connecting to their Servers.

Right now I am just about to lose my mind over this.

From my monitoring of the netstat command at the time I try to connect I see that several processes( including ms-sql-s,ssdp,microsoft-ds) call the external machine with a SYN_SENT packet which is never acknowledged by the server. I don't know whether the SQL server machine ever recieves the packet from my own server as the ISP won't check their firewall logs to see what machines have connected to their machines.

I can ping and a pathping works perfectly but there is a problem with nslookup. It seems that an nslookup on the server name points to a different IP address(and name) than the actual server. But I felt that since I created an Alias in the Client Network Utility the need for DNS lookup would be bypassed. Any suggestions on this?

Please any help on this would be greatly appreciated!

I am currently wondering whether the fact that I have not updated the MSDE to SP4( but I have updated the Main SQL Server to SP4) but I didn't think this was a big issue.

Another thing that could be an issue is the fact that the SQL Service Account seems to work under a System Account. Could this be the problem?

I have listed the environment under which the SQL Server is running under below:

Operating System : Windows Server 2003 (SP1) running under AD domain
SQL Server: 8.0.2039(SP4) and MSDE not updated

Please I really need assistance with this!

Thank you!!

When you looks into an abyss, the abyss looks also into you-- Friedrich Nietsczhe
Go to Top of Page
   

- Advertisement -