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 |
|
esthera
Master Smack Fu Yak Hacker
1410 Posts |
Posted - 2007-03-25 : 08:23:27
|
| when i connect to sql from the same machine i use mserver="newserver\SQLEXPRESS"what would i use connecting from another machinei tried the ipaddress\SQLEXPRESSand if didn't work |
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2007-03-25 : 09:52:45
|
you can use any of the below- newserver\SQLEXPRESS- ipaddress\SQLEXPRESS- newserver,<port no>- ipaddress,<port no>for SQL Server 2005, remote access to the SQL Server is turn off by default. You need to turn it on via the Surface Area Config tool. I am not sure is it the same for SQLExpress. KH |
 |
|
|
esthera
Master Smack Fu Yak Hacker
1410 Posts |
Posted - 2007-03-25 : 10:14:14
|
| these didn't work -- any other ideas? remote connections are turned on. |
 |
|
|
t.summerfield
Starting Member
7 Posts |
Posted - 2007-03-26 : 12:13:48
|
| HiFrom my experience I recommend changing the TCP/IP port from 1433 (usually blocked on routers because its heavily targetted by virus') It may not fix your problem, but is a common problem with remote connections.On your server machine open "SQL Server Configuration Manager" and navigate to SQL Server 2005 Network Configuration. Under Protocols for <server name> right click TCP/IP and select properties, then select the IP Addresses tab and change the TCP ports. You will need to do the same under SQL Native Client Configuration, Client protocols, TCP/IPDo the same on the client machine under Client Protocols and Aliases (if applicable)Hope this helpsRegardsToby |
 |
|
|
|
|
|