RE: SQL Server Access
- From: Jesper Hauge <JesperHauge@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 05:27:07 -0700
I've figured it out for myself - problem was not in the Access control as i
thought. The server has multiple IP-addresses, turns out that the SBS-did'nt
assign the servers network name to the same IP-adress as previously, so the
SQL-server is not listening on the IP-address the SBS-server has registered
in the WINS database.
Sorry for the inconveniece.
..Jesper
"Jesper Hauge" wrote:
> Hello all
>
> I've recently switched from a P2P workgroup to a SBS2003 Domain. Basically
> I've installed a new server runnning SBS, and then used
> sbsserver/connectcomputer to add my existing workstations and Windows 2003
> server to the domain.
>
> My problem is that I am no longer able to connect to the SQL server running
> on the other Win2003 server via Enteprise manager on my workstation. Heres
> what I have already tried:
>
> - I've checked that the SQL server is communication via TCP/IP on port 1433,
> I can connect via telnet to port 1433 on the server.
>
> - I've added the "domain\Power Users" group of which my windows account is a
> member to the "security/logins" section of the enterprise manager on the
> server and checked the "System administrators" role for this group.
>
> - I've tried using the "sa" account for remote access via Enterprise Manager
> and Query Analyzer, but I recieve the same error message as when I am using
> my windows account.
>
> What am I missing? Help and comments very much appreciated.
>
> Regards
> Jesper Hauge
.
- Follow-Ups:
- RE: SQL Server Access
- From: "Charles Yang [MSFT]"
- RE: SQL Server Access
- References:
- SQL Server Access
- From: Jesper Hauge
- SQL Server Access
- Prev by Date: Problems when offer remote assistance
- Next by Date: Re: Outlook 2003 client
- Previous by thread: SQL Server Access
- Next by thread: RE: SQL Server Access
- Index(es):
Relevant Pages
|