sql reports: network

Showing posts with label network. Show all posts

Tuesday, March 27, 2012

can we connect?

can we connect named instance through IP like in the network utility I just
defined the IP of the server where the named instance installed and define
the port...
Client Netowork Utility > Alias >
Alias: MyServer
Server: 209.45.23.55
Port : 1434
Protocol: TCP/IP
any thing else I need to do for connecting this... I did the above stuff but
I had failed to connect but why I can connect the default instance... please
guide me..
Thanks and I would highly appreciate if your prompt reply
thanks and have a great day
Hi,
Open the SQL Server error log under the folder
SQL_Server_installation_path>X\MSSQL$instance_name \LOG folder to make sure
that the SQL Server named instance runs well and to find the TCP port which
this named instance is listening.
As well as using Server network utility verify TCP/IP protocol is enabled.
Get the SQL Server name from Error log and use that name to connect from
query analyzer
Thanks
Hari
SQL Server MVP
"Rogers" <Rogers@.discussions.microsoft.com> wrote in message
news:DC15100C-5AC0-4C51-9CA3-8527DBF3DC23@.microsoft.com...
> can we connect named instance through IP like in the network utility I
> just
> defined the IP of the server where the named instance installed and define
> the port...
> Client Netowork Utility > Alias >
> Alias: MyServer
> Server: 209.45.23.55
> Port : 1434
> Protocol: TCP/IP
> any thing else I need to do for connecting this... I did the above stuff
> but
> I had failed to connect but why I can connect the default instance...
> please
> guide me..
> Thanks and I would highly appreciate if your prompt reply
> thanks and have a great day
>
|||First of all Hari, thanks for your reply... I can easily connect the named
instance on that same machine ... I am trying to connect that named instance
through my client machine and facing this problem...
"Hari Prasad" wrote:

> Hi,
> Open the SQL Server error log under the folder
> SQL_Server_installation_path>X\MSSQL$instance_nam e\LOG folder to make sure
> that the SQL Server named instance runs well and to find the TCP port which
> this named instance is listening.
> As well as using Server network utility verify TCP/IP protocol is enabled.
> Get the SQL Server name from Error log and use that name to connect from
> query analyzer
> Thanks
> Hari
> SQL Server MVP
>
> "Rogers" <Rogers@.discussions.microsoft.com> wrote in message
> news:DC15100C-5AC0-4C51-9CA3-8527DBF3DC23@.microsoft.com...
>
>

Sunday, March 25, 2012

Can we backup to a remote drive?

Please let me know. Can we backup SQL Server database to a network drive?Yes.
From the backup command you'll want to use a UNC drive reference such as
\\servername\share
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?|||Yes, and you must use UNC format, not mapped drive.
btw, you still keep the tie?
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?|||"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:uGmoZZaHEHA.3240@.TK2MSFTNGP12.phx.gbl...
> Yes.
> From the backup command you'll want to use a UNC drive reference such as
> \\servername\share
Providing it's a disk share. Tape drives must be locally connected
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.655 / Virus Database: 420 - Release Date: 08/04/2004|||Hi,
There are Few Pre requisites to do this;
1. Should have share in the remote machine
2. You Should start SQL server using Domain user who got access to remote
machine Share
3. If you need to schedule this as a job then SQL Agent should use the same
Domain user in which SQL server was started
4. Restart the services
Now you can execute the Backup script with UNC path
BACKUP Database <dbname> to disk='\\computername\sharename\dbname.bak' with
init
Note:
Backup to remote machine will not work if you start SQL server using Local
system account
Thanks
Hari
MCDBA
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?sql

Can we backup to a remote drive?

Please let me know. Can we backup SQL Server database to a network drive?
Yes.
From the backup command you'll want to use a UNC drive reference such as
\\servername\share
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?
|||Yes, and you must use UNC format, not mapped drive.
btw, you still keep the tie?
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?
|||"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:uGmoZZaHEHA.3240@.TK2MSFTNGP12.phx.gbl...
> Yes.
> From the backup command you'll want to use a UNC drive reference such as
> \\servername\share
Providing it's a disk share. Tape drives must be locally connected
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.655 / Virus Database: 420 - Release Date: 08/04/2004
|||Hi,
There are Few Pre requisites to do this;
1. Should have share in the remote machine
2. You Should start SQL server using Domain user who got access to remote
machine Share
3. If you need to schedule this as a job then SQL Agent should use the same
Domain user in which SQL server was started
4. Restart the services
Now you can execute the Backup script with UNC path
BACKUP Database <dbname> to disk='\\computername\sharename\dbname.bak' with
init
Note:
Backup to remote machine will not work if you start SQL server using Local
system account
Thanks
Hari
MCDBA
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?

Can we backup to a remote drive?

Please let me know. Can we backup SQL Server database to a network drive?Yes.
From the backup command you'll want to use a UNC drive reference such as
\\servername\share
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?|||Yes, and you must use UNC format, not mapped drive.
btw, you still keep the tie?
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?|||"Brian Moran" <brian@.solidqualitylearning.com> wrote in message
news:uGmoZZaHEHA.3240@.TK2MSFTNGP12.phx.gbl...
> Yes.
> From the backup command you'll want to use a UNC drive reference such as
> \\servername\share
Providing it's a disk share. Tape drives must be locally connected
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.655 / Virus Database: 420 - Release Date: 08/04/2004|||Hi,
There are Few Pre requisites to do this;
1. Should have share in the remote machine
2. You Should start SQL server using Domain user who got access to remote
machine Share
3. If you need to schedule this as a job then SQL Agent should use the same
Domain user in which SQL server was started
4. Restart the services
Now you can execute the Backup script with UNC path
BACKUP Database <dbname> to disk='\\computername\sharename\dbname.bak' with
init
Note:
Backup to remote machine will not work if you start SQL server using Local
system account
Thanks
Hari
MCDBA
"Bill Clinton" <anonymous@.discussions.microsoft.com> wrote in message
news:25D36DC8-F721-460B-9A81-D259078DED22@.microsoft.com...
> Please let me know. Can we backup SQL Server database to a network drive?

Friday, February 24, 2012

can someone login as "NT AUTHORITY\SYSTEM "

Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
one of our servers. I log both the failed and successful logins and both of
the above logins were used recently. Do they have passwords that can be set?
What would be the implications if I removed both of them from
"security/logins"? I'm running both the server service and agent service with
a different login so it wouldn't affect the jobs.
Thanks,
--
Dan D.Hi Dan
These are the name of the accounts when you specify local system or network
service as the accounts in which a service runs under see
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
John
"Dan D." wrote:
> Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> one of our servers. I log both the failed and successful logins and both of
> the above logins were used recently. Do they have passwords that can be set?
> What would be the implications if I removed both of them from
> "security/logins"? I'm running both the server service and agent service with
> a different login so it wouldn't affect the jobs.
> Thanks,
> --
> Dan D.|||I came across an article today about how someone could log in as NT AUTHORITY
through the cmd window using the task scheduler and I got a little concerned.
Thanks for the article.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> These are the name of the accounts when you specify local system or network
> service as the accounts in which a service runs under see
> http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> John
> "Dan D." wrote:
> > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > one of our servers. I log both the failed and successful logins and both of
> > the above logins were used recently. Do they have passwords that can be set?
> >
> > What would be the implications if I removed both of them from
> > "security/logins"? I'm running both the server service and agent service with
> > a different login so it wouldn't affect the jobs.
> >
> > Thanks,
> > --
> > Dan D.|||Hi Dan
Could you can post a link to the article?
John
"Dan D." wrote:
> I came across an article today about how someone could log in as NT AUTHORITY
> through the cmd window using the task scheduler and I got a little concerned.
> Thanks for the article.
> --
> Dan D.
>
> "John Bell" wrote:
> > Hi Dan
> >
> > These are the name of the accounts when you specify local system or network
> > service as the accounts in which a service runs under see
> > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> >
> > John
> >
> > "Dan D." wrote:
> >
> > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > one of our servers. I log both the failed and successful logins and both of
> > > the above logins were used recently. Do they have passwords that can be set?
> > >
> > > What would be the implications if I removed both of them from
> > > "security/logins"? I'm running both the server service and agent service with
> > > a different login so it wouldn't affect the jobs.
> > >
> > > Thanks,
> > > --
> > > Dan D.|||Sometimes the page doesn't render correctly. You may have to scroll down to
see the beginning of the article.
http://www.ozzu.com/ftopic1337.html
--
Dan D.
"John Bell" wrote:
> Hi Dan
> Could you can post a link to the article?
> John
> "Dan D." wrote:
> > I came across an article today about how someone could log in as NT AUTHORITY
> > through the cmd window using the task scheduler and I got a little concerned.
> > Thanks for the article.
> > --
> > Dan D.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi Dan
> > >
> > > These are the name of the accounts when you specify local system or network
> > > service as the accounts in which a service runs under see
> > > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> > >
> > > John
> > >
> > > "Dan D." wrote:
> > >
> > > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > > one of our servers. I log both the failed and successful logins and both of
> > > > the above logins were used recently. Do they have passwords that can be set?
> > > >
> > > > What would be the implications if I removed both of them from
> > > > "security/logins"? I'm running both the server service and agent service with
> > > > a different login so it wouldn't affect the jobs.
> > > >
> > > > Thanks,
> > > > --
> > > > Dan D.|||Hi Dan
The article is talking about a vunerability highlighted in
http://support.microsoft.com/?kbid=823980 that can be exploited by a specific
worm, rather than something actually logging in a the account. You should
make sure that your system is patched to a level which does not have this
issue. Tools like Microsoft Baseline Security Advisor will help you configure
your systems check out http://msdn2.microsoft.com/en-us/library/aa302360.aspx
John
"Dan D." wrote:
> Sometimes the page doesn't render correctly. You may have to scroll down to
> see the beginning of the article.
> http://www.ozzu.com/ftopic1337.html
> --
> Dan D.
>
> "John Bell" wrote:
> > Hi Dan
> >
> > Could you can post a link to the article?
> >
> > John
> >
> > "Dan D." wrote:
> >
> > > I came across an article today about how someone could log in as NT AUTHORITY
> > > through the cmd window using the task scheduler and I got a little concerned.
> > > Thanks for the article.
> > > --
> > > Dan D.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Dan
> > > >
> > > > These are the name of the accounts when you specify local system or network
> > > > service as the accounts in which a service runs under see
> > > > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> > > >
> > > > John
> > > >
> > > > "Dan D." wrote:
> > > >
> > > > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > > > one of our servers. I log both the failed and successful logins and both of
> > > > > the above logins were used recently. Do they have passwords that can be set?
> > > > >
> > > > > What would be the implications if I removed both of them from
> > > > > "security/logins"? I'm running both the server service and agent service with
> > > > > a different login so it wouldn't affect the jobs.
> > > > >
> > > > > Thanks,
> > > > > --
> > > > > Dan D.|||Thanks. I do run the Baseline Security Analyzer.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> The article is talking about a vunerability highlighted in
> http://support.microsoft.com/?kbid=823980 that can be exploited by a specific
> worm, rather than something actually logging in a the account. You should
> make sure that your system is patched to a level which does not have this
> issue. Tools like Microsoft Baseline Security Advisor will help you configure
> your systems check out http://msdn2.microsoft.com/en-us/library/aa302360.aspx
> John
> "Dan D." wrote:
> > Sometimes the page doesn't render correctly. You may have to scroll down to
> > see the beginning of the article.
> >
> > http://www.ozzu.com/ftopic1337.html
> >
> > --
> > Dan D.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi Dan
> > >
> > > Could you can post a link to the article?
> > >
> > > John
> > >
> > > "Dan D." wrote:
> > >
> > > > I came across an article today about how someone could log in as NT AUTHORITY
> > > > through the cmd window using the task scheduler and I got a little concerned.
> > > > Thanks for the article.
> > > > --
> > > > Dan D.
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Dan
> > > > >
> > > > > These are the name of the accounts when you specify local system or network
> > > > > service as the accounts in which a service runs under see
> > > > > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> > > > >
> > > > > John
> > > > >
> > > > > "Dan D." wrote:
> > > > >
> > > > > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > > > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > > > > one of our servers. I log both the failed and successful logins and both of
> > > > > > the above logins were used recently. Do they have passwords that can be set?
> > > > > >
> > > > > > What would be the implications if I removed both of them from
> > > > > > "security/logins"? I'm running both the server service and agent service with
> > > > > > a different login so it wouldn't affect the jobs.
> > > > > >
> > > > > > Thanks,
> > > > > > --
> > > > > > Dan D.|||Hi Dan
Hopefully you have patched this, make sure that you keep your MBSA up to date.
John
"Dan D." wrote:
> Thanks. I do run the Baseline Security Analyzer.
> --
> Dan D.
>
> "John Bell" wrote:
> > Hi Dan
> >
> > The article is talking about a vunerability highlighted in
> > http://support.microsoft.com/?kbid=823980 that can be exploited by a specific
> > worm, rather than something actually logging in a the account. You should
> > make sure that your system is patched to a level which does not have this
> > issue. Tools like Microsoft Baseline Security Advisor will help you configure
> > your systems check out http://msdn2.microsoft.com/en-us/library/aa302360.aspx
> >
> > John
> >
> > "Dan D." wrote:
> >
> > > Sometimes the page doesn't render correctly. You may have to scroll down to
> > > see the beginning of the article.
> > >
> > > http://www.ozzu.com/ftopic1337.html
> > >
> > > --
> > > Dan D.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Dan
> > > >
> > > > Could you can post a link to the article?
> > > >
> > > > John
> > > >
> > > > "Dan D." wrote:
> > > >
> > > > > I came across an article today about how someone could log in as NT AUTHORITY
> > > > > through the cmd window using the task scheduler and I got a little concerned.
> > > > > Thanks for the article.
> > > > > --
> > > > > Dan D.
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi Dan
> > > > > >
> > > > > > These are the name of the accounts when you specify local system or network
> > > > > > service as the accounts in which a service runs under see
> > > > > > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "Dan D." wrote:
> > > > > >
> > > > > > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > > > > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > > > > > one of our servers. I log both the failed and successful logins and both of
> > > > > > > the above logins were used recently. Do they have passwords that can be set?
> > > > > > >
> > > > > > > What would be the implications if I removed both of them from
> > > > > > > "security/logins"? I'm running both the server service and agent service with
> > > > > > > a different login so it wouldn't affect the jobs.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > --
> > > > > > > Dan D.

can someone login as "NT AUTHORITY\SYSTEM "

Tuesday, February 14, 2012

Can only log into a MSDE ODBC Connection as Administrator

When trying to log into a ODBC connection as a power user on a network we
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
access denied.
Change the user to Administrator and they are able to login.
Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:

>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does not exist or
>access denied.
>Change the user to Administrator and they are able to login.
|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:

> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setup
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:

> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>
|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain where
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC setup
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help. I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:

> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>

Can only log into a MSDE ODBC Connection as Administrator

When trying to log into a ODBC connection as a power user on a network we
receive the following error:
Connection failed:
SQLState:'01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibbe
ct ()),
Connection failed:
SQLState:'08001'
SQL server Error:178
[microsoft][odbc sql server driver][dbnetlib]sql server does not
exist or
access denied.
Change the user to Administrator and they are able to login.Did you add logins for other users who aren't members of the
local admin group on the box where MSDE is installed? It
sounds like they may not have logins setup in MSDE.
By default, members of the local admins group will have
access. For other users, you need to add logins.
-Sue
On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:

>When trying to log into a ODBC connection as a power user on a network we
>receive the following error:
>Connection failed:
>SQLState:'01000'
>SQL Server Error: 53
>[Microsoft][ODBC SQL Server Driver][DBNET]ConnectionOpen (/cibb
ect ()),
>Connection failed:
>SQLState:'08001'
>SQL server Error:178
>[microsoft][odbc sql server driver][dbnetlib]sql server does no
t exist or
>access denied.
>Change the user to Administrator and they are able to login.|||Sue,
Yes I did add them to the system as a user. Then created an MSDE Group.
The Group has the following rights:
GROUP EVERYONE - Read to Program Files
MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
FOLDER
USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED WE
GET THE FOLLOWING ERROR:
AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
I APPRECIATE YOUR HELP.
"Sue Hoegemeier" wrote:

> Did you add logins for other users who aren't members of the
> local admin group on the box where MSDE is installed? It
> sounds like they may not have logins setup in MSDE.
> By default, members of the local admins group will have
> access. For other users, you need to add logins.
> -Sue
> On Thu, 27 Oct 2005 19:25:02 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>|||No need to yell. Using caps is considered yelling in
newsgroups.
By adding the users as logins in SQL Server, that doesn't
have anything to do with adding them to groups on the box
where MSDE is running.
How exactly are you trying to connect? I think something is
missing here as mapping drives is not necessary, giving
users full control on MSDE folders, etc is generally not
necessary either.
-Sue
On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>Yes I did add them to the system as a user. Then created an MSDE Group.
>The Group has the following rights:
> GROUP EVERYONE - Read to Program Files
> MSDE GROUP DOES NOT HAVE FULL CONTROL, NO DEL FOLDERS, TAKE OWNERSHIP,
>CREATE FOLDER OR CHANGE PERMISSION TO THE MSDE/SYSTEM FOLDER OR MSDE/SERVER
>FOLDER
>USING A NOTEBOOK WITH ENTERPRISE MANAGER WE HAD GIVE THE MSDE GROUP -
>PUBLIC, DB_WRITER, DB_READER AND DB_BACKUP OPERATOR
>APPLIED SERVICE PACK 2 TO THE SYSTEM THAT IS RUNNING THE MSDE SERVICE AND
>NOW THE SYSTEM RUNNING ENTERPRISE MANAGER GETS THE FOLLOWING ERROR WHEN
>ATTEMPTING TO CONNECT TO THE SYSTEM MAP DRIVE THAT HAS THE MSDE INSTALLED W
E
>GET THE FOLLOWING ERROR:
>AN ERROR OCCURRED WHILE RECONNECTING TO A LOCAL CONNECTION . MICROSOFT
>WINDOWN NETWORK. THE LOCAL DEVICE NAME IS ALREADY IN USE.
>CANNOT CONNECT THE ENTERPRISE MANAGER TO THE MSDE DATABASE NOW.
>I APPRECIATE YOUR HELP.
>
>"Sue Hoegemeier" wrote:
>|||I apologize I did not know that caps were yelling, I am happy for the help.
Since we are testing this on our network, I am logging into our domain where
both systems reside. The MSDE is running on an XP workstation and we have
other workstations attempting to log into it. When we go into the ODBC setu
p
we can see the MSDE instance but cannot log on to it.
Bonnie
"Sue Hoegemeier" wrote:

> No need to yell. Using caps is considered yelling in
> newsgroups.
> By adding the users as logins in SQL Server, that doesn't
> have anything to do with adding them to groups on the box
> where MSDE is running.
> How exactly are you trying to connect? I think something is
> missing here as mapping drives is not necessary, giving
> users full control on MSDE folders, etc is generally not
> necessary either.
> -Sue
> On Fri, 28 Oct 2005 15:13:03 -0700, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>|||No problem...figured you just didn't know about the caps
thing. Anyway, check the event logs on the XP workstation
where MSDE is running to see if there are any security
errors. Make sure the MSDE instance is listening on TCP/IP
and that the clients are configure to connect with TCP/IP.
You would probably want to start by running through the
following article - it's long but connectivity issues aren't
real easy to resolve as it can be so many different things.
Potential causes of the "SQL Server does not exist or access
denied" error message
http://support.microsoft.com/?id=328306
-Sue
On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
<bw@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I apologize I did not know that caps were yelling, I am happy for the help.
>Since we are testing this on our network, I am logging into our domain wher
e
>both systems reside. The MSDE is running on an XP workstation and we have
>other workstations attempting to log into it. When we go into the ODBC set
up
>we can see the MSDE instance but cannot log on to it.
>Bonnie
>
>"Sue Hoegemeier" wrote:
>|||Sue,
We found out we were using the wrong port for MSDE. MSDE was listening on
Port 1143. We were using the SQL default of 1443 Thank you for your help.
I
have another question now that this one is resolved. I'll start a new
thread. Thank you again for your help.
"Sue Hoegemeier" wrote:

> No problem...figured you just didn't know about the caps
> thing. Anyway, check the event logs on the XP workstation
> where MSDE is running to see if there are any security
> errors. Make sure the MSDE instance is listening on TCP/IP
> and that the clients are configure to connect with TCP/IP.
> You would probably want to start by running through the
> following article - it's long but connectivity issues aren't
> real easy to resolve as it can be so many different things.
> Potential causes of the "SQL Server does not exist or access
> denied" error message
> http://support.microsoft.com/?id=328306
> -Sue
> On Mon, 31 Oct 2005 07:01:07 -0800, "bw"
> <bw@.discussions.microsoft.com> wrote:
>
>

Sunday, February 12, 2012

Can not remotely connect to instance of sql server 2000

I had a big problem on connecting sqlserver remotely from other machines on the network .....

From any computer in the network i wanna to register the instance of the sqlserver from the enterprise manager ..... the server instance doesn't appear within the available sqlserver list (the servername which equal to my machine is the only one that appear) ..... when i manualy write the servername\alias manually and i choose the connection type and then i write sqlserver username and password and then finish he give a message to me that access denied or sql server doesn't exist ... !!

by the way from the local machine i registered the local instance of sqlserver successfully and successfully i access the Databases .....

To be noted:

I previously uninstalled this alias and i then i reinstalled it again with the same name and i attached the previously exists Databes.

in the same time i installed on the same machine sqlserver 2005 connectivity clients not the server itself.

Why are you using aliases? Do select @.@.servername, and tell me if this is the exact name you're trying to connect to via enterprise manager.|||

thank you for trying to help me,

I am using an alias from a long time and it was working good until i uninstalled the server and installed it agian .......

when i make "select @.@.servername" it return back "magedsalah\maged" and as i told before it works well on the local machine where i can connect with the enterprise manager to magedsalah\maged without any problems ......

the problem when anybody wanna to register magedsalah\maged in the enterprise manager of another computer the magedsalah\maged doesn't appear in the servers list what appear is magedsalah and it can't be registered and sometimes and some there is nothing appear at all.....

for further details plz refer to original message in the thread.....

thanks

|||Did you ever figure out the solution to this, I'm having the exact same problem, it occured after I installed Sql 2005, and now i'm using named instances.|||

Hi,

After i trapped in solving this problem ..... i removed the existing sql server 2000 where i use the alias and then i installed it again without alias (the default case in setup) ..... then i reattached my databases ......... and it works fine now

|||

I ended up doing the same thing too, and mine works too now. There must be a trick to making it work with alias'/instance names too though, oh well.

Thanks

Tuesday, March 27, 2012

can we connect?

Sunday, March 25, 2012

Can we backup to a remote drive?

Can we backup to a remote drive?

Can we backup to a remote drive?

Friday, February 24, 2012

can someone login as "NT AUTHORITY\SYSTEM "

can someone login as "NT AUTHORITY\SYSTEM "

can someone login as "NT AUTHORITY\SYSTEM "

Tuesday, February 14, 2012

Can only log into a MSDE ODBC Connection as Administrator

Can only log into a MSDE ODBC Connection as Administrator

Sunday, February 12, 2012

Can not remotely connect to instance of sql server 2000

sql reports

Blog Archive

About Me