Connection issue to sql 2005 behind firewall.... TCP vs. Named pipes

Hello,
I know this topic has been covered pretty heavily, but i've not come accross a solution that is specific enough to our issue.  We are moving to SQL 2005 for a web app. We have Firewalls between the IIS 6 Web Server and the Sql Server 2005 (64bit if that makes a difference).

If we try to close down the ports between the servers then the application that talks to the sql server gets the access is denied or Server does not exist error. If i open it up to IP Any it works fine.
TCP any with UDP any doesn't work either. I've tried running ethereal on it but i can't see any port connections besides teh 1433 and 1434.

On the SQL Server both TCP and named pipes are allowed for remote connections. but how can i tell if it's using TCP? And shouldn't that work with TCP 1433 and UDP 1434?

I know we are using a named instance on the server as we have to change the connection string to ip\instance_name but does that mean we are using named pipes?

Thanks!
LVL 1
tonkajeep34Asked:
Who is Participating?
 
DBAduck - Ben MillerConnect With a Mentor Principal ConsultantCommented:
Here is the KB article that I talked about.
http://support.microsoft.com/kb/287932

Not sure what I was thinking when I hit submit last time.
Ben.
0
 
DBAduck - Ben MillerPrincipal ConsultantCommented:
You would use TCP over a firewall and not named pipes.  Here is a KB article about TCP and firewalls for SQL Sverer.

Ben.
0
 
YveauCommented:
The issue is in the named instance !!
I've been breaking my head over the same issue. I could not find a real sollution, so I stopped when I had this workable workaround ... but it's not the ideal situation !

Create on the connecting server an alias for DBMSserver\instance thant looks like DBMSserver_instance (omit the '\' character !) ... it worked for me ... but don't ask me why.

Big disadvantage is that you have to create an alias on every connecting machine that has this problem. Big advantage is that you only have to change something on machines that have an issue.

Good luck !
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
tonkajeep34Author Commented:
dbaduck, Could you post that link again?

Yes i want to use TCP but i'm not sure if it is or not and how to tell. Obviously the issue is that when i close down the firewall to what i've read TCP uses it doesn't work so i'm assuming that it is using named pipes instead of tcp. but i don't know what will happen if i just go and change the surface config to be tcp only.

Thanks
0
 
tonkajeep34Author Commented:
Yveau,

What type of alias did you create? was it an odbc data source or like an alias in the host file? I'd like to give it a try just not sure which one to try yet.

Thanks
0
 
YveauCommented:
Sorry, should have been more specific. A SQL alias. Use the SQL Server configuration manager and then under the 'SQL Native Client Configuration' you can create an alias.

Good luck.
0
 
YveauCommented:
tonkajeep34,

Is your Q answered or can I be any more assistance ?
0
 
tonkajeep34Author Commented:
Sorry i forgot to reply. Our DBA tried that and it still didn't work. I think he's decided it's time to call M$ support.

Thanks,
Mike
0
 
YveauCommented:
If we can't help you any more, can you please close the Q ?
Thanks !
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.