This is also the SERVER network utility and NOT the CLIENT network utility. This entry exists on the SQL Server, NOT on the client.

The Client Network Utility does support...

Well, I would disagree. I have never used an lmhosts file and do not recommend doing it. I have not had a single problem implementing the way I...

I would NOT suggest transformable subscriptions unless you are already 100% comfortable with all aspects of replication. Doing so makes it impossible to validate that you are synchronized, troubleshooting...

You can use a domain account. You just have to deal with multi-domain trust issues and all the rest of those problems which you can't normally control. It...

With a MASSIVE difference when dealing with cluster failover, version of SQL Server, etc. If you are hitting SQL Server 2000, it is much cleaner. Doing it against...

None of that is necessary and won't fix or solve the problem.

Create a local account on each machine that has the same name and password. Make this account a...

Well, you are going to have a mess. Why? Because replication is designed to keep the data in synch. It is not designed for "Keep my data...

You have to use IP addresses to make this work. The first hurdle is getting through the firewall/proxy server. You need to startup the Server Network Utility on...

It does not populate because merge is managed by a set of triggers behind the replicated tables. These triggers are coded to ignore anything that is done using a...