Community
Showing results for 
Search instead for 
Do you mean 
Reply

2010 & Server 2008 64 bit

New Member
Posts: 3
Country: United States

2010 & Server 2008 64 bit

I got 2010 prem for web running on a 2008 Standard server.  It runs the web fine, However, I cannot open the db from the windows clients.

 

1. I have opened the firewalls on both the clients and the server for port 1433 (standard sql port)

2. The user has the right to the directory.

3. They can add, delete and create files in the directories.

4. AV is McAfee

 

The error that I'm getting is the network connection error message - any thought?

Platinum Elite Contributor
Posts: 14,384
Country: Australia
New Member
Posts: 3
Country: United States

Re: 2010 & Server 2008 64 bit

Thanks Mike, I tried all of those - feedback

 

 

The list
1. I can check and uncheck "share database" - database is shared.
2. The shared folder is set to "everyone" having "full control"
3. compatibility mode - no joy.
4. Computer name has not been changed.
5. Pad file pointed in the right place.
6. Detached and recreated pad file anyway. - no joy
7. Versions are the same.12.0.409.0, Hotfix 3 - updated both anyway - no joy.
8. act7 and browser are both started and running. -
9. tcp/ip is enabled on both client and server, inidently, there is a grammar error on that page item 4.
  "If you did make have to make a change and enable these protocols"
10. Opened all the ports as per http://support.microsoft.com/kb/968872 - no joy; while the workstations have McAfee, my test workstation is not running any AV (its also a 2008 32 bit server).
11. Its not a compressed drive ... The server is a win server2008 64 bit running under Hyper-V
12.  There are not multiple shares.
13 The client machines can all see and log into the server.  I've tried editing the PAD file so that it accesses the IP directly and this did not solve it.
Any further thoughts?

 

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: 2010 & Server 2008 64 bit

Not without looking at the system. But I can tell you, if you are getting the error on the KB, the problem will be one of the listed items