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 |
|
mswyatt
Starting Member
3 Posts |
 Posted - 2003-03-13 : 10:23:24
|
| Hi,I have some users who work through a VPN and are having troubleconnecting to a SQL server. Installing the SQL Server 2000 Client Network Utility works, but I don't want to have to send the CD to all of my remote users.Is there a way to distribute just the SQL Server Client Network Utility installation files to my users? I tried the sqlredis.exe file but that didn't seem to do the trick.Thanks for the help,michael |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-03-13 : 12:19:09
|
| What do the clients need out of the Client Network Utility? This utility is just used to modify the registry. You could simply send them the registry entry needed to connect to your SQL Server. Here is an example of a registry file (just save it as <filename>.reg and have them double click on the file after they have it on their machine):Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo]"Server1"="DBMSSOCN,Server1,1433"Client Network Utility does nothing more than this. If they need anything other than this, then they should just install MDAC, which will give them everything else that they need. Client do not need the SQL Server installation CD.Tara |
 |
|
|
mswyatt
Starting Member
3 Posts |
Posted - 2003-03-13 : 16:07:44
|
| Tara, Thanks for your reply and help. I tried exporting the entry from my registry and importing it to another machine, but that did not fix the problem. I also downloaded and installed MDAC 2.7 SP1 from Microsoft and that did not fix the problem either. To describe the problem more, I have created a SQL Server database that is listening on port 1433. I am using ERwin Data Modeler to connect to the SQL db and it works fine when I am at work. Users working from home cannot connect, receiving a message that the SQL server in unavailable. The home users can create an ODBC connection and specify a specific port number and the ODBC connection works, but still not ERwin. ERwin support suggested installing the Client Tools. I have installed the Client Connectivity Tools from the SQL Server 2000 CD on my machine and it works from the office and from home. Even after removing (through Add/Remove Programs) it still works. Not sure what else SQL Client Tools installs, but it did something to my machine. I have a fix, but I didn't want to have to make copies of the SQL Server CD to send to everyone. Thanks again for the help. michael |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-03-13 : 16:12:26
|
| I am a little confused now. In your initial post, you said that you had to install the Client Network Utility. Now you are saying the Client tools. The Client Network Utility is one of the things that you get when you install the Client tools. I haven't used ERwin in a few months, but I believe that you can set it up so that it points to an ODBC DSN connection rather than using the SQL native driver. Just have them point to the DSN instead.Tara |
|
|
|
mswyatt
Starting Member
3 Posts |
Posted - 2003-03-14 : 15:07:57
|
| Tara,I guess your confusion stems from my newness to the SQL Server world. :-) I installed the Client Connectivity (Client Tools)component of the SQL Server and just assumed the Client Network Utility was the only thing besides MDAC that was installed.ERwin help says you can used an ODBC connection, but I have not been able to figure out how to configure it. There is no choice for an ODBC connection in the DBMS connection pulldown. And ERwin support told me that I had to have the Client Tools installed. So, I'm just looking for the easiest way to distribute them. If I have to, I will just make a few copies of the CD and send it out. I was just hoping for something a little more elegant.Thanks again for your help.michael |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-03-14 : 15:15:15
|
| Your users will probably need the Client tools anyway even if they weren't using ERwin. Any kind of development in SQL Server would require the Client tools being installed. I would suspect that some of your users would prefer not to use ERwin since it is very limiting in what it can do (as compared to the Client tools).If you do not want to pass out the installation CD, then you might want to consider doing this through SMS. SMS would allow the deployment of the Client tools to specific users. I would talk to your server administrators and find out if they have SMS or any other software deployment tool. I'm not sure if the home users would be able to get the installation though through VPN, but I would bet that your server administrators would know the answer to it.Tara |
|
|
|
|
|
|
|
|
(Newbie) SQL Server 2000 Client Network Utility