Can access it locally but cannot access it from other work stations.
I am assuming it is some sort of logon error, being it is not a
domain. Any ideas on getting by this ?Two possible issues.
One it's installed on Win XP with service pack 2. SP2 has an automatic
firewall that you will need to punch a hole through.
Two the SQL Server is configured for Windows only authentication. Since you
can access it locally you are probably a member of the local administrators
group and as such are granted sa rights by default. Windows only
authentication will not work for remote connections in a work group. You
will need to use SQL Server standard security in mixed mode.
Hope this helps,
Danny
"Father Jack Hackett" <Jachack@.rcc.org> wrote in message
news:j8r4q0djmla88go6hdbraesv6nl4n4d3cd@.4ax.com...
> Hi have a small network setup and have MS sql server on workstation.
> Can access it locally but cannot access it from other work stations.
> I am assuming it is some sort of logon error, being it is not a
> domain. Any ideas on getting by this ?|||I have been trying to set it up on a local workgroup with all XP home
edition computers, I am running into the same problem.
Lionel
On Tue, 23 Nov 2004 12:45:16 GMT, "Danny" <istdrs@.flash.net> wrote:
>Two possible issues.
>One it's installed on Win XP with service pack 2. SP2 has an automatic
>firewall that you will need to punch a hole through.
>Two the SQL Server is configured for Windows only authentication. Since you
>can access it locally you are probably a member of the local administrators
>group and as such are granted sa rights by default. Windows only
>authentication will not work for remote connections in a work group. You
>will need to use SQL Server standard security in mixed mode.
>Hope this helps,
>Danny
>
>"Father Jack Hackett" <Jachack@.rcc.org> wrote in message
>news:j8r4q0djmla88go6hdbraesv6nl4n4d3cd@.4ax.com...
>> Hi have a small network setup and have MS sql server on workstation.
>> Can access it locally but cannot access it from other work stations.
>> I am assuming it is some sort of logon error, being it is not a
>> domain. Any ideas on getting by this ?
No comments:
Post a Comment