MS sql server on workgroup not domain.

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 ?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 ?

MS SQL Port

How can I determine which port MS SQL is running.
I known that this can be set at SQL Server Network Utility, but I
wonder why my ASP.NET script can connect to SQL Server even I change
its running port.

Another thing I want to know... actually it doesn't concern with SQL
that is,
how can I watch all the enviroment variable in Windows XP, such as
%systemroot% and how can I set that one"=aKe=" <darkgod1987@.hotmail.com> wrote in message
news:36e545c4.0404140338.6b6e5440@.posting.google.c om...
> How can I determine which port MS SQL is running.
> I known that this can be set at SQL Server Network Utility, but I
> wonder why my ASP.NET script can connect to SQL Server even I change
> its running port.
> Another thing I want to know... actually it doesn't concern with SQL
> that is,
> how can I watch all the enviroment variable in Windows XP, such as
> %systemroot% and how can I set that one

You can look in the SQL Server Log for the port, in the registry, or use the
SQLDMO Registry2 object's TcpPort property.

SQL Server listens on two ports - 1433 and 1434 (by default). A client can
connect to port 1434 to get connection information about all the instances
on the server, inclluding their ports. See "Controlling Net-Libraries and
Communications Addresses" in Books Online.

As for environment variables, you can use SET in the Windows shell, or use
an interface such as WMI which returns all the current variables. WSH has a
built-in object for this, I believe, perhaps the Network object but I'm not
entirely sure.

Simon

MS SQL Backup

I'm trying to backup a database in MS SQL 7. I want to backup to a network directory. I'm running into problems when I give the path to a network directory. MS SQL tells me it is not a valid path. Then if I try to browes to the directory i want it does not see any of the networked drives.

Why does MS SQL only see local drives?

Has anyone delt with this problem before? Any suggestions would be greatly appriciated.

Thanks,

AnimaulYeah, its pretty annoying isn't it. Fortunately there is a solution. In Enterprise Manager under the Management folder there is a icon call backup. This is really a backup device (like a hard drive or network share). Just right click on the backup icon and choose new backup device. Give the device a name and for the file name type in the network path something like:
\\ServerName\foldername\filename.bck, you will probably get a warning that sql can't verify the path & filename but thats ok.

Then when you go to create the backup choose add and then pick the new backup device you just created from the dropdown list.

later,
mkal|||Thanks! That was a huge help.

Animaul