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.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2001-11-18 : 17:52:25
|
| Kevin writes "Hello! Here's a challenge for you... I've been struggling with it for too long. Posted on other newsgroups, they haven't touched this one... so I'll give as many details as I can.OUR SETUP: I'm attempting snapshot replication from our development server to our web server, (both W2KServer:SP2, SQL7:SP3). The dev server is on our LAN behind a firewall. The web server is alone behind another firewall. Since this replication is over the internet, we must use a Pull Subscription. WHERE I'M STUCK NOW:On the web server I keep getting these entries in the Job History for the Pull Subscription:1)Connecting to Subscriber 'NATASHA'2)Connecting to Distributor 'SPIDERMAN'3)Initializing4)Connecting to ftp site '64.213.162.203'5)Category:OS Source: Number:12029 Message: A connection with the server could not be established6)The process could not connect to FTP site '64.213.162.203' using port 21. The step failed.ARTICLES I've been using:1) "INF: Replication Setup Over a Firewall" MS Knowledge Base #Q164667-We opened firewall ports and made registry changes as specified. It's intended for 6.5 but is about the only article out there on this. Anyway I think(!) I'm past this point now.2) "Managing Replication Security" SQL7 Books Online-For the user the subscription logs in with, I've given the rights: serverrole=sysadmin, dbaccess=db_owner.-This user I also entered in to the PAL.3) "Configuring a Publication to Use FTP" SQL7 Books Online-In IIS I made the ftp home dir: MSSQL7_Data\REPLDATA\FTP -- I see the schema, index, and bulk-copy files in another subfolder here-I also checked to see that @enabled_for_internet property = 14) "Configuring a Subscription to Use FTP" SQL7 Books Online-I left the default port as 21 (both servers)-It says the FTP addressing properties are for the Distribution Agent to use... Does it have access to these from the pull subscription properties? ...just trying to think of anything that might prevent the necessary connections.5) "Snapshot Replication" SQL7 Books Online-According to this article, it appears that the snapshot files are where they should be.SOME TESTS and checks I've made:1) It seems the firewall -- with port 1433 for SQL7, & ports for RPC traffic open (as per #Q164667) -- is not the issue now since the log shows nothing being blocked.2) SQL7 on the web server is getting through to SQL7 on the dev machine. Because if I stop SQL7 on the dev server, or change a parameter in the pull subscription properties only(such as ftp user password), I get different error messages, ie: "SQL Server not found", or "Login fails for user..."3) On the dev server: The SQL Agent startup account is a member of administrators, so it should have rights that it needs.4) W2K Event Viewer on the dev server does not show any warnings or clues after I run the pull subscription job on the web server.What is the best way to troubleshoot and find what connection is not being made? Maybe I'm taking the wrong approach somewhere. But seems like its so close to working.-One thing I'm not sure about & might cause a problem is the dev server has an IP internal to our network, but I'm using an IP in both the Client Network Utility & Pull Subscr Properties on the web server (outside of our LAN) that our firewall then maps to this internal IP. But again it's finding that machine... so maybe this is not a problem.-Should I try to find more on error# 12029, or is it just attached to the "...not be established" message?-How can I dig deeper to troubleshoot this?Any ideas?? At all??Getting this to work is going past my employer's budget!! Don't know where to go from here...Thanks for ANY response, (if you need more details please let me know)Kevin(p.s. this seems long... but char count is < 3800)" |
|
|
|
|
|
|
|
Help! - Pull Subscription errors in replication over a firewall