- May 8, 2006
- 842
- 0
- 0
Hello all,
I have been deploying SQL servers for the past 10 years. I know SQL can be a pain but have always managed to succeed.
Now i have a small application that uses a small SQL database. I installed SQL 2008 Express + SP1 on a Windows 7 HomeBasic x86 OS (I have a license for that version). But i cant manage to allow the client computer (two computers should use the application and database) to connect to the database. Everything functions locally but the second computer says it can't find the SQL server. I am doing everything right, IP protocols, allowed remote access and everything. I cant make even Management studio express to connect to the server saying naming problem to the server and instance occurred.
Since i managed to install everything and get it to work on Windows Server 2008 + SQL2008, i am starting to think that there might be some problem with the Windows version. Do you have any knowledge whether the HomeBasic is screwing things up or is it just something i am missing?
I have been deploying SQL servers for the past 10 years. I know SQL can be a pain but have always managed to succeed.
Now i have a small application that uses a small SQL database. I installed SQL 2008 Express + SP1 on a Windows 7 HomeBasic x86 OS (I have a license for that version). But i cant manage to allow the client computer (two computers should use the application and database) to connect to the database. Everything functions locally but the second computer says it can't find the SQL server. I am doing everything right, IP protocols, allowed remote access and everything. I cant make even Management studio express to connect to the server saying naming problem to the server and instance occurred.
Since i managed to install everything and get it to work on Windows Server 2008 + SQL2008, i am starting to think that there might be some problem with the Windows version. Do you have any knowledge whether the HomeBasic is screwing things up or is it just something i am missing?
