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 |
|
scottpt
Posting Yak Master
186 Posts |
 Posted - 2005-09-12 : 15:03:30
|
| I can ping IP address. I can Ping DNS name. I used free ping to ping the port and the port is open. From the server I can connect to the server, but from my desktop I cannot. It gives me Sql server not found error.It makes no sense. Has anybody had anything this bizzare happen before? |
|
|
scottpt
Posting Yak Master
186 Posts |
Posted - 2005-09-12 : 15:04:05
|
| Also, I can term srv into the box and see that it is up and available. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2005-09-12 : 15:05:19
|
| Add an alias on your client machine using Client Network Utility. Make sure to specify the port that SQL Server is listening on in the alias.Tara |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-09-12 : 15:20:40
|
| What OS/Service pack are you running? What service pack of SQL are you running?what port are you pinging? Is UDP port 1434 to your server blocked?-ecEDIT:This is most easily tested using the portqry tool from microsoft. http://support.microsoft.com/kb/832919/ at the bottom of the article is a download link for portqryUI, which gives you a gui to use. |
|
|
|
madness
Starting Member
13 Posts |
Posted - 2005-09-13 : 17:24:29
|
| Try connection to the server using the ip address followed by the port number. ie 192.168.1.1,1433This will force the connection to use TCP protocol and means it doesn;t need to use 1434 port to determine what port the sql server is running on |
|
|
|
daquoc
Starting Member
35 Posts |
Posted - 2005-09-18 : 23:43:38
|
| I think you should check the client Configulation when you make new data source and use TCP/IP option in Network Library Configuration.May be. |
|
|
|
|
|
|
Cannot Connect to server