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 |
|
Drathnar
Starting Member
8 Posts |
 Posted - 2007-10-09 : 15:57:41
|
| I am having a problem with one of the PC's That remotely connects to my server. When you go to connection properties (under Connect to server in the Management studio) on the users machine there are no options under Network Protocol only the <default> option.All the rest of our PC's have the option of choosing TCP/IP , named pipe etc etc..This computer is not able to connect to the server remotely however it can/does when it is on the network. I figure its because it is attempting to connect over named pipe rather than TCP/IP but i cannot change this in the connection options as it is missing.And as far as i know on the server i have the default set to TCP/IP but I am really unsure of this.If anyone can help me out with this i would greatly appreciate it. |
|
|
Drathnar
Starting Member
8 Posts |
Posted - 2007-10-09 : 16:27:56
|
| And i don't know if this is helpful or not in trying to figure this out but when connecting to the server the user types in servername which is an alias on the serveralias nameservernameserverservernameprotocolnpservername\pipe\sql\query are the paramaters |
 |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-10-09 : 22:48:22
|
| Do you mean there is alias defined on that client machine? Did you check if tcp/ip is enabled in configuration manager -> sql native client on that machine? |
|
|
|
Drathnar
Starting Member
8 Posts |
Posted - 2007-10-10 : 09:11:43
|
| The alias is defined on the serverthe client has no aliases TCP/IP is enabled we don't have a problem connecting on most pc's its just his for some reason and i believe its because nothing shows up in the dropdown menu of his connection options to choose to connect by TCP/IP or NP etc.. In the end i would like some insight as to why nothing would show up in his dropdown menu to be able to choose how he would like to connect |
|
|
|
Drathnar
Starting Member
8 Posts |
Posted - 2007-10-10 : 09:14:16
|
| I ran an Osql string to the server using stcp and i get that the server does not accept remote connections however running the same string on a pc that works the results come back fine.Everyone connects remotely through a cisco VPN client I am under the impression that we may have different versions I don't know if this would/could possibly be the cause. |
|
|
|
Drathnar
Starting Member
8 Posts |
Posted - 2007-10-10 : 14:23:37
|
| What ports by default need to be opened to allow remote access using the management studio? 1433 tcp i know is one does 1434 udp need to be opened also and any other ports? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-10 : 14:48:21
|
quote:
Originally posted by Drathnar
The alias is defined on the serverthe client has no aliases
Aliases are useless on the server unless the server is trying to connect to another server, such as when using client tools from the server or a linked server. In both cases, the server is acting as a client.Aliases need to be on the clients.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-10-10 : 14:49:32
|
quote:
Originally posted by Drathnar
What ports by default need to be opened to allow remote access using the management studio? 1433 tcp i know is one does 1434 udp need to be opened also and any other ports?
1433 needs to be opened if the server is using 1433. We don't use 1433 here when the application is Internet-facing. If you are using aliases, then you don't need 1434 as the client knows exactly how to talk to the server with an alias.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
Network Protocols