Named Pipes and Instances problems

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

SQL Server Administration (2000)

Named Pipes and Instances problems

Author

Topic

bogey
Posting Yak Master

166 Posts

Posted - 2005-09-30 : 10:59:00

I'm having a few problems with some of our users who are in a different domain than I am. My network people are thinking that my sql server 2000 box is the culprit and I'm saying its a firewall issue. Now I've removed the named pipes option and are using tcp/ip only. Users are connection/trying to connect to an "Instance".

The network people say that even though I've "turned off" named pipes, the sql server is still using them??

Can this be true? If I have tcp/ip checked then that is what is used nom matter if its a default instance or one that I've setup myself

Thanks.

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2005-09-30 : 14:45:44

tell us more about the actual problem you are having. Are people having a problem connecting to your instance? what error are they getting?

Is there a firewall between the domain that your SQL Server is on and the domain where the users having the problem are located? Are the network guys filtering out UDP port 1434?

-ec

bogey
Posting Yak Master

166 Posts

Posted - 2005-09-30 : 15:19:29

The users and sql server are in differnt domains and there is a firewall between them.

Here is the error message that the end user is getting
[DBNETLIB]Invalid connection.
[DBNETLIB]ConnectionOpen (Invalid Instance()).

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2005-09-30 : 16:02:47

ask your network admins if they are filtering UDP port 1434 with the firewall.

You can do a test on your own by using the portqry tool here http://support.microsoft.com/default.aspx?scid=kb;en-us;265808. I recommend using the portqryUI tool (link at bottom of KB article). You can use this tool to determine if UDP port 1434 is open.

This is imporatant because SQL2000 uses UDP port 1434 in a kind of 3 way handshake when you first connect. If you cannot get through 1434, then your connection will fail.

There is a workaround to this (if the firewall config cannot be altered), and I will get to that after you test to see if 1434 is open or not.

-ec

bogey
Posting Yak Master

166 Posts

Posted - 2005-10-03 : 09:43:03

We do not allow port 1434.

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2005-10-03 : 09:48:37

quote:
Originally posted by bogey

We do not allow port 1434.

that is the problem then.

you will have to create aliases using the sql client configuration tool. Here are the steps:

1. start client config tool, type 'cliconfg' from the command prompt
2. Click the aliases tab
3. Click add button
4. Type a name at the top for server alias, this can include '\' if it is a named instance
5. Make sure TCP/IP is selected
6. Type server name below, this cannot include the '\', just the hostname
7. uncheck dynamically determine port
8. type in port number used by your instance.
9. Test connection using Data Sources control panel

If this is a defualt instance, then the port is 1433. If this is a named instance it will have been randomly selected at instance install time. If you do not know the port number used by your sql server, you can find this out easily enough by using the server network utility from the console of your SQL Server.

-ec

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2005-10-03 : 12:29:12

Make sure all the users also have the latest MDAC. Old MDAC components won't recognize instances. That's a possibility you need to check.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

eyechart
Master Smack Fu Yak Hacker

3575 Posts

Posted - 2005-10-03 : 14:32:09

quote:
Originally posted by derrickleggett

Make sure all the users also have the latest MDAC. Old MDAC components won't recognize instances. That's a possibility you need to check.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.

definitely check the MDAC release. If these are win2k machines then the MDAC could be out of date. If they are winxp systems then you should be ok.

However, If port 1434 UDP is blocked, you will have to make the alias I referred to above regardless of the MDAC release.

-ec

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources