Cannot connect a remote SQL server 2005...
-
Hi, I have one machine (PC-A) running XP Pro and SQL Server 2005, and another machine (PC-B) running XP Pro and Visual Studio 2005. Both are on my local network. They can see each other. On PC-B, I tried to connect to PC-A SQL Server, but failed. PC-A SQL Server is allowing remote connections. Windows Authentication is used for connections. What else did I not set right? Thanks!
Best, Jun
-
Hi, I have one machine (PC-A) running XP Pro and SQL Server 2005, and another machine (PC-B) running XP Pro and Visual Studio 2005. Both are on my local network. They can see each other. On PC-B, I tried to connect to PC-A SQL Server, but failed. PC-A SQL Server is allowing remote connections. Windows Authentication is used for connections. What else did I not set right? Thanks!
Best, Jun
AFAIK you may have to add rules to your server's firewall, so it allows inbound traffic on TCP port 1433, and possibly also UDP port 1434. If it still fails to connect, watch the error message closely; stuff it in the Google search box and/or show it here. :)
Luc Pattyn [My Articles] Nil Volentibus Arduum
-
AFAIK you may have to add rules to your server's firewall, so it allows inbound traffic on TCP port 1433, and possibly also UDP port 1434. If it still fails to connect, watch the error message closely; stuff it in the Google search box and/or show it here. :)
Luc Pattyn [My Articles] Nil Volentibus Arduum
Thabks for reply. After I added TCP port 1433 and UDP port 1434 to PC-A firewall exceptions and tested connection, I got the error "Login failed for user 'PC-A\Guest'". How can I set up Windows Authentication login properly? In my case, it is not a domain environment. There is no common domain account, but individual accounts on each machine.
Best, Jun
-
Thabks for reply. After I added TCP port 1433 and UDP port 1434 to PC-A firewall exceptions and tested connection, I got the error "Login failed for user 'PC-A\Guest'". How can I set up Windows Authentication login properly? In my case, it is not a domain environment. There is no common domain account, but individual accounts on each machine.
Best, Jun
I don't know how to do that with Windows authentication; I did solve it once using SQL Authentication: just give your database and your app the same username and password, so tje DB can be accessed from everywhere by anyone running your app. May not be the safest way, but it works. :)
Luc Pattyn [My Articles] Nil Volentibus Arduum
-
I don't know how to do that with Windows authentication; I did solve it once using SQL Authentication: just give your database and your app the same username and password, so tje DB can be accessed from everywhere by anyone running your app. May not be the safest way, but it works. :)
Luc Pattyn [My Articles] Nil Volentibus Arduum