Hello All,

I am trying to provide remote access "ONLY" to SQL server on our SBS 2003
Premium ASAP so he can access only SQL server for development purposes.

Any Ideas how I can accomplish this.

Thanx.

Re: SQL Developer Remote Access by MF

MF
Thu Jul 10 13:08:00 PDT 2008

Thanx Costas for your response. I would think a specific database would be
the most secure option, but then again, I am not too familiar with creating a
specific database to then restrict access to. I would love help in that area
as well.

Thanx again.



"Costas" wrote:

> Do you want the developer to have access to the SQL Server or a specific
> database within SQL Server?
>
> --
> Costas
> http://costas.cpstechgroup.com
>
>
>
> "MF" <MF@discussions.microsoft.com> wrote in message
> news:97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com...
> > Hello All,
> >
> > I am trying to provide remote access "ONLY" to SQL server on our SBS 2003
> > Premium ASAP so he can access only SQL server for development purposes.
> >
> > Any Ideas how I can accomplish this.
> >
> > Thanx.
>

Re: SQL Developer Remote Access by Costas

Costas
Thu Jul 10 13:39:58 PDT 2008

We might be OT, discussing SQL Server issues on the SBS forum and hopefully
others will be OK with it.

Run SQL Server Management Studio (as Administrator) and connect to your SQL
Server, using Windows Authentication. If 'Object Explorer' is not visible,
open it from the 'View' menu item.

Click on 'Security' and right-click on 'Logins'. Click 'New Login'. Click
the 'Search' button next to the 'Login Name'. Make sure the location is set
to the domain name (See: 'From this location') Add the user account you want
to have access to the database and click 'OK'. You just created a Login
object for user. Click 'OK' again.

Now right click on the 'Databases' folder and select 'New Database'. Give
the database a name, next to the 'Owner' field click the button, and type
the login name you just created. If you don't type the domain name a window
will show up with the name that matches what you typed. Click the checkbox
next to the login and then 'OK'. Under 'Database Files' you'll see the name
of the the database and the log. To the right, under 'Path', is the place
on the hard drive where you specify where you want the files stored. You
can change that path if you like. Click 'OK'.

This is the quick and dirty way. There are other options that need to be
set, but the developer should be able to set them since s/he is the db
owner.

Hope that helps

--
Costas
http://costas.cpstechgroup.com



"MF" <MF@discussions.microsoft.com> wrote in message
news:10BB7401-929C-450B-833D-2E53B234C4EA@microsoft.com...
> Thanx Costas for your response. I would think a specific database would be
> the most secure option, but then again, I am not too familiar with
> creating a
> specific database to then restrict access to. I would love help in that
> area
> as well.
>
> Thanx again.
>
>
>
> "Costas" wrote:
>
>> Do you want the developer to have access to the SQL Server or a specific
>> database within SQL Server?
>>
>> --
>> Costas
>> http://costas.cpstechgroup.com
>>
>>
>>
>> "MF" <MF@discussions.microsoft.com> wrote in message
>> news:97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com...
>> > Hello All,
>> >
>> > I am trying to provide remote access "ONLY" to SQL server on our SBS
>> > 2003
>> > Premium ASAP so he can access only SQL server for development purposes.
>> >
>> > Any Ideas how I can accomplish this.
>> >
>> > Thanx.
>>


Re: SQL Developer Remote Access by MF

MF
Thu Jul 10 14:16:03 PDT 2008

Thanx Costas,

I was able to do exactly how you explained and all seems to be set. It just
remains how to make the database accessible remotely over an IP
network/internet.

Thanx again.



"Costas" wrote:

> We might be OT, discussing SQL Server issues on the SBS forum and hopefully
> others will be OK with it.
>
> Run SQL Server Management Studio (as Administrator) and connect to your SQL
> Server, using Windows Authentication. If 'Object Explorer' is not visible,
> open it from the 'View' menu item.
>
> Click on 'Security' and right-click on 'Logins'. Click 'New Login'. Click
> the 'Search' button next to the 'Login Name'. Make sure the location is set
> to the domain name (See: 'From this location') Add the user account you want
> to have access to the database and click 'OK'. You just created a Login
> object for user. Click 'OK' again.
>
> Now right click on the 'Databases' folder and select 'New Database'. Give
> the database a name, next to the 'Owner' field click the button, and type
> the login name you just created. If you don't type the domain name a window
> will show up with the name that matches what you typed. Click the checkbox
> next to the login and then 'OK'. Under 'Database Files' you'll see the name
> of the the database and the log. To the right, under 'Path', is the place
> on the hard drive where you specify where you want the files stored. You
> can change that path if you like. Click 'OK'.
>
> This is the quick and dirty way. There are other options that need to be
> set, but the developer should be able to set them since s/he is the db
> owner.
>
> Hope that helps
>
> --
> Costas
> http://costas.cpstechgroup.com
>
>
>
> "MF" <MF@discussions.microsoft.com> wrote in message
> news:10BB7401-929C-450B-833D-2E53B234C4EA@microsoft.com...
> > Thanx Costas for your response. I would think a specific database would be
> > the most secure option, but then again, I am not too familiar with
> > creating a
> > specific database to then restrict access to. I would love help in that
> > area
> > as well.
> >
> > Thanx again.
> >
> >
> >
> > "Costas" wrote:
> >
> >> Do you want the developer to have access to the SQL Server or a specific
> >> database within SQL Server?
> >>
> >> --
> >> Costas
> >> http://costas.cpstechgroup.com
> >>
> >>
> >>
> >> "MF" <MF@discussions.microsoft.com> wrote in message
> >> news:97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com...
> >> > Hello All,
> >> >
> >> > I am trying to provide remote access "ONLY" to SQL server on our SBS
> >> > 2003
> >> > Premium ASAP so he can access only SQL server for development purposes.
> >> >
> >> > Any Ideas how I can accomplish this.
> >> >
> >> > Thanx.
> >>
>

Re: SQL Developer Remote Access by MF

MF
Thu Jul 10 14:28:01 PDT 2008

In addition to how to make it available remotely, I was confused about the
setup part where I had to choose an authentication type; Windows
Wuthentication or SQL Server Authentication. WHich is appropriate for this
scenario where the developer only needs access to the databse and nothing
else on the server?

Thanx.



"MF" wrote:

> Thanx Costas,
>
> I was able to do exactly how you explained and all seems to be set. It just
> remains how to make the database accessible remotely over an IP
> network/internet.
>
> Thanx again.
>
>
>
> "Costas" wrote:
>
> > We might be OT, discussing SQL Server issues on the SBS forum and hopefully
> > others will be OK with it.
> >
> > Run SQL Server Management Studio (as Administrator) and connect to your SQL
> > Server, using Windows Authentication. If 'Object Explorer' is not visible,
> > open it from the 'View' menu item.
> >
> > Click on 'Security' and right-click on 'Logins'. Click 'New Login'. Click
> > the 'Search' button next to the 'Login Name'. Make sure the location is set
> > to the domain name (See: 'From this location') Add the user account you want
> > to have access to the database and click 'OK'. You just created a Login
> > object for user. Click 'OK' again.
> >
> > Now right click on the 'Databases' folder and select 'New Database'. Give
> > the database a name, next to the 'Owner' field click the button, and type
> > the login name you just created. If you don't type the domain name a window
> > will show up with the name that matches what you typed. Click the checkbox
> > next to the login and then 'OK'. Under 'Database Files' you'll see the name
> > of the the database and the log. To the right, under 'Path', is the place
> > on the hard drive where you specify where you want the files stored. You
> > can change that path if you like. Click 'OK'.
> >
> > This is the quick and dirty way. There are other options that need to be
> > set, but the developer should be able to set them since s/he is the db
> > owner.
> >
> > Hope that helps
> >
> > --
> > Costas
> > http://costas.cpstechgroup.com
> >
> >
> >
> > "MF" <MF@discussions.microsoft.com> wrote in message
> > news:10BB7401-929C-450B-833D-2E53B234C4EA@microsoft.com...
> > > Thanx Costas for your response. I would think a specific database would be
> > > the most secure option, but then again, I am not too familiar with
> > > creating a
> > > specific database to then restrict access to. I would love help in that
> > > area
> > > as well.
> > >
> > > Thanx again.
> > >
> > >
> > >
> > > "Costas" wrote:
> > >
> > >> Do you want the developer to have access to the SQL Server or a specific
> > >> database within SQL Server?
> > >>
> > >> --
> > >> Costas
> > >> http://costas.cpstechgroup.com
> > >>
> > >>
> > >>
> > >> "MF" <MF@discussions.microsoft.com> wrote in message
> > >> news:97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com...
> > >> > Hello All,
> > >> >
> > >> > I am trying to provide remote access "ONLY" to SQL server on our SBS
> > >> > 2003
> > >> > Premium ASAP so he can access only SQL server for development purposes.
> > >> >
> > >> > Any Ideas how I can accomplish this.
> > >> >
> > >> > Thanx.
> > >>
> >

Re: SQL Developer Remote Access by Costas

Costas
Thu Jul 10 14:56:36 PDT 2008

I just realized that the developer will not be within the organization. I
think we are talking the wrong approach to this issue. The developer
doesn't have to have access to SQL Server at all in order to develop the
application. He can develop locally at their location and when they are
ready to deploy they create the database part of the system at your
location.

That's the proper way to do it (unless I'm missing something)

--
Costas
http://costas.cpstechgroup.com



"MF" <MF@discussions.microsoft.com> wrote in message
news:883D21B7-2FF5-4327-876C-AA6B62F6FBF2@microsoft.com...
> In addition to how to make it available remotely, I was confused about the
> setup part where I had to choose an authentication type; Windows
> Wuthentication or SQL Server Authentication. WHich is appropriate for this
> scenario where the developer only needs access to the databse and nothing
> else on the server?
>
> Thanx.
>
>
>
> "MF" wrote:
>
>> Thanx Costas,
>>
>> I was able to do exactly how you explained and all seems to be set. It
>> just
>> remains how to make the database accessible remotely over an IP
>> network/internet.
>>
>> Thanx again.
>>
>>
>>
>> "Costas" wrote:
>>
>> > We might be OT, discussing SQL Server issues on the SBS forum and
>> > hopefully
>> > others will be OK with it.
>> >
>> > Run SQL Server Management Studio (as Administrator) and connect to your
>> > SQL
>> > Server, using Windows Authentication. If 'Object Explorer' is not
>> > visible,
>> > open it from the 'View' menu item.
>> >
>> > Click on 'Security' and right-click on 'Logins'. Click 'New Login'.
>> > Click
>> > the 'Search' button next to the 'Login Name'. Make sure the location
>> > is set
>> > to the domain name (See: 'From this location') Add the user account you
>> > want
>> > to have access to the database and click 'OK'. You just created a
>> > Login
>> > object for user. Click 'OK' again.
>> >
>> > Now right click on the 'Databases' folder and select 'New Database'.
>> > Give
>> > the database a name, next to the 'Owner' field click the button, and
>> > type
>> > the login name you just created. If you don't type the domain name a
>> > window
>> > will show up with the name that matches what you typed. Click the
>> > checkbox
>> > next to the login and then 'OK'. Under 'Database Files' you'll see the
>> > name
>> > of the the database and the log. To the right, under 'Path', is the
>> > place
>> > on the hard drive where you specify where you want the files stored.
>> > You
>> > can change that path if you like. Click 'OK'.
>> >
>> > This is the quick and dirty way. There are other options that need to
>> > be
>> > set, but the developer should be able to set them since s/he is the db
>> > owner.
>> >
>> > Hope that helps
>> >
>> > --
>> > Costas
>> > http://costas.cpstechgroup.com
>> >
>> >
>> >
>> > "MF" <MF@discussions.microsoft.com> wrote in message
>> > news:10BB7401-929C-450B-833D-2E53B234C4EA@microsoft.com...
>> > > Thanx Costas for your response. I would think a specific database
>> > > would be
>> > > the most secure option, but then again, I am not too familiar with
>> > > creating a
>> > > specific database to then restrict access to. I would love help in
>> > > that
>> > > area
>> > > as well.
>> > >
>> > > Thanx again.
>> > >
>> > >
>> > >
>> > > "Costas" wrote:
>> > >
>> > >> Do you want the developer to have access to the SQL Server or a
>> > >> specific
>> > >> database within SQL Server?
>> > >>
>> > >> --
>> > >> Costas
>> > >> http://costas.cpstechgroup.com
>> > >>
>> > >>
>> > >>
>> > >> "MF" <MF@discussions.microsoft.com> wrote in message
>> > >> news:97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com...
>> > >> > Hello All,
>> > >> >
>> > >> > I am trying to provide remote access "ONLY" to SQL server on our
>> > >> > SBS
>> > >> > 2003
>> > >> > Premium ASAP so he can access only SQL server for development
>> > >> > purposes.
>> > >> >
>> > >> > Any Ideas how I can accomplish this.
>> > >> >
>> > >> > Thanx.
>> > >>
>> >


Re: SQL Developer Remote Access by MF

MF
Thu Jul 10 15:13:03 PDT 2008

The whole idea is for the developer to developer directly on our server as
opposed to develope on their server and port over for deployment. How is this
possible?

Thanx.



"Costas" wrote:

> I just realized that the developer will not be within the organization. I
> think we are talking the wrong approach to this issue. The developer
> doesn't have to have access to SQL Server at all in order to develop the
> application. He can develop locally at their location and when they are
> ready to deploy they create the database part of the system at your
> location.
>
> That's the proper way to do it (unless I'm missing something)
>
> --
> Costas
> http://costas.cpstechgroup.com
>
>
>
> "MF" <MF@discussions.microsoft.com> wrote in message
> news:883D21B7-2FF5-4327-876C-AA6B62F6FBF2@microsoft.com...
> > In addition to how to make it available remotely, I was confused about the
> > setup part where I had to choose an authentication type; Windows
> > Wuthentication or SQL Server Authentication. WHich is appropriate for this
> > scenario where the developer only needs access to the databse and nothing
> > else on the server?
> >
> > Thanx.
> >
> >
> >
> > "MF" wrote:
> >
> >> Thanx Costas,
> >>
> >> I was able to do exactly how you explained and all seems to be set. It
> >> just
> >> remains how to make the database accessible remotely over an IP
> >> network/internet.
> >>
> >> Thanx again.
> >>
> >>
> >>
> >> "Costas" wrote:
> >>
> >> > We might be OT, discussing SQL Server issues on the SBS forum and
> >> > hopefully
> >> > others will be OK with it.
> >> >
> >> > Run SQL Server Management Studio (as Administrator) and connect to your
> >> > SQL
> >> > Server, using Windows Authentication. If 'Object Explorer' is not
> >> > visible,
> >> > open it from the 'View' menu item.
> >> >
> >> > Click on 'Security' and right-click on 'Logins'. Click 'New Login'.
> >> > Click
> >> > the 'Search' button next to the 'Login Name'. Make sure the location
> >> > is set
> >> > to the domain name (See: 'From this location') Add the user account you
> >> > want
> >> > to have access to the database and click 'OK'. You just created a
> >> > Login
> >> > object for user. Click 'OK' again.
> >> >
> >> > Now right click on the 'Databases' folder and select 'New Database'.
> >> > Give
> >> > the database a name, next to the 'Owner' field click the button, and
> >> > type
> >> > the login name you just created. If you don't type the domain name a
> >> > window
> >> > will show up with the name that matches what you typed. Click the
> >> > checkbox
> >> > next to the login and then 'OK'. Under 'Database Files' you'll see the
> >> > name
> >> > of the the database and the log. To the right, under 'Path', is the
> >> > place
> >> > on the hard drive where you specify where you want the files stored.
> >> > You
> >> > can change that path if you like. Click 'OK'.
> >> >
> >> > This is the quick and dirty way. There are other options that need to
> >> > be
> >> > set, but the developer should be able to set them since s/he is the db
> >> > owner.
> >> >
> >> > Hope that helps
> >> >
> >> > --
> >> > Costas
> >> > http://costas.cpstechgroup.com
> >> >
> >> >
> >> >
> >> > "MF" <MF@discussions.microsoft.com> wrote in message
> >> > news:10BB7401-929C-450B-833D-2E53B234C4EA@microsoft.com...
> >> > > Thanx Costas for your response. I would think a specific database
> >> > > would be
> >> > > the most secure option, but then again, I am not too familiar with
> >> > > creating a
> >> > > specific database to then restrict access to. I would love help in
> >> > > that
> >> > > area
> >> > > as well.
> >> > >
> >> > > Thanx again.
> >> > >
> >> > >
> >> > >
> >> > > "Costas" wrote:
> >> > >
> >> > >> Do you want the developer to have access to the SQL Server or a
> >> > >> specific
> >> > >> database within SQL Server?
> >> > >>
> >> > >> --
> >> > >> Costas
> >> > >> http://costas.cpstechgroup.com
> >> > >>
> >> > >>
> >> > >>
> >> > >> "MF" <MF@discussions.microsoft.com> wrote in message
> >> > >> news:97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com...
> >> > >> > Hello All,
> >> > >> >
> >> > >> > I am trying to provide remote access "ONLY" to SQL server on our
> >> > >> > SBS
> >> > >> > 2003
> >> > >> > Premium ASAP so he can access only SQL server for development
> >> > >> > purposes.
> >> > >> >
> >> > >> > Any Ideas how I can accomplish this.
> >> > >> >
> >> > >> > Thanx.
> >> > >>
> >> >
>

Re: SQL Developer Remote Access by Costas

Costas
Thu Jul 10 15:58:31 PDT 2008

Here are a couple of links that guide you on how to do that.

http://msdn.microsoft.com/en-us/library/ms175483.aspx
http://msdn.microsoft.com/en-us/library/ms177440.aspx
http://support.microsoft.com/kb/316898

The other solution is to give the developer a domain account and allow
him/her VPN access. That will simplify things since you won't have to
publish the db on the Net.


--
Costas
http://costas.cpstechgroup.com



"MF" <MF@discussions.microsoft.com> wrote in message
news:6E21F9E3-50EA-48AE-8084-8C7B7651C449@microsoft.com...
> The whole idea is for the developer to developer directly on our server as
> opposed to develope on their server and port over for deployment. How is
> this
> possible?
>
> Thanx.
>
>
>
> "Costas" wrote:
>
>> I just realized that the developer will not be within the organization.
>> I
>> think we are talking the wrong approach to this issue. The developer
>> doesn't have to have access to SQL Server at all in order to develop the
>> application. He can develop locally at their location and when they are
>> ready to deploy they create the database part of the system at your
>> location.
>>
>> That's the proper way to do it (unless I'm missing something)
>>
>> --
>> Costas
>> http://costas.cpstechgroup.com
>>
>>
>>
>> "MF" <MF@discussions.microsoft.com> wrote in message
>> news:883D21B7-2FF5-4327-876C-AA6B62F6FBF2@microsoft.com...
>> > In addition to how to make it available remotely, I was confused about
>> > the
>> > setup part where I had to choose an authentication type; Windows
>> > Wuthentication or SQL Server Authentication. WHich is appropriate for
>> > this
>> > scenario where the developer only needs access to the databse and
>> > nothing
>> > else on the server?
>> >
>> > Thanx.
>> >
>> >
>> >
>> > "MF" wrote:
>> >
>> >> Thanx Costas,
>> >>
>> >> I was able to do exactly how you explained and all seems to be set. It
>> >> just
>> >> remains how to make the database accessible remotely over an IP
>> >> network/internet.
>> >>
>> >> Thanx again.
>> >>
>> >>
>> >>
>> >> "Costas" wrote:
>> >>
>> >> > We might be OT, discussing SQL Server issues on the SBS forum and
>> >> > hopefully
>> >> > others will be OK with it.
>> >> >
>> >> > Run SQL Server Management Studio (as Administrator) and connect to
>> >> > your
>> >> > SQL
>> >> > Server, using Windows Authentication. If 'Object Explorer' is not
>> >> > visible,
>> >> > open it from the 'View' menu item.
>> >> >
>> >> > Click on 'Security' and right-click on 'Logins'. Click 'New Login'.
>> >> > Click
>> >> > the 'Search' button next to the 'Login Name'. Make sure the
>> >> > location
>> >> > is set
>> >> > to the domain name (See: 'From this location') Add the user account
>> >> > you
>> >> > want
>> >> > to have access to the database and click 'OK'. You just created a
>> >> > Login
>> >> > object for user. Click 'OK' again.
>> >> >
>> >> > Now right click on the 'Databases' folder and select 'New Database'.
>> >> > Give
>> >> > the database a name, next to the 'Owner' field click the button, and
>> >> > type
>> >> > the login name you just created. If you don't type the domain name a
>> >> > window
>> >> > will show up with the name that matches what you typed. Click the
>> >> > checkbox
>> >> > next to the login and then 'OK'. Under 'Database Files' you'll see
>> >> > the
>> >> > name
>> >> > of the the database and the log. To the right, under 'Path', is the
>> >> > place
>> >> > on the hard drive where you specify where you want the files stored.
>> >> > You
>> >> > can change that path if you like. Click 'OK'.
>> >> >
>> >> > This is the quick and dirty way. There are other options that need
>> >> > to
>> >> > be
>> >> > set, but the developer should be able to set them since s/he is the
>> >> > db
>> >> > owner.
>> >> >
>> >> > Hope that helps
>> >> >
>> >> > --
>> >> > Costas
>> >> > http://costas.cpstechgroup.com
>> >> >
>> >> >
>> >> >
>> >> > "MF" <MF@discussions.microsoft.com> wrote in message
>> >> > news:10BB7401-929C-450B-833D-2E53B234C4EA@microsoft.com...
>> >> > > Thanx Costas for your response. I would think a specific database
>> >> > > would be
>> >> > > the most secure option, but then again, I am not too familiar with
>> >> > > creating a
>> >> > > specific database to then restrict access to. I would love help in
>> >> > > that
>> >> > > area
>> >> > > as well.
>> >> > >
>> >> > > Thanx again.
>> >> > >
>> >> > >
>> >> > >
>> >> > > "Costas" wrote:
>> >> > >
>> >> > >> Do you want the developer to have access to the SQL Server or a
>> >> > >> specific
>> >> > >> database within SQL Server?
>> >> > >>
>> >> > >> --
>> >> > >> Costas
>> >> > >> http://costas.cpstechgroup.com
>> >> > >>
>> >> > >>
>> >> > >>
>> >> > >> "MF" <MF@discussions.microsoft.com> wrote in message
>> >> > >> news:97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com...
>> >> > >> > Hello All,
>> >> > >> >
>> >> > >> > I am trying to provide remote access "ONLY" to SQL server on
>> >> > >> > our
>> >> > >> > SBS
>> >> > >> > 2003
>> >> > >> > Premium ASAP so he can access only SQL server for development
>> >> > >> > purposes.
>> >> > >> >
>> >> > >> > Any Ideas how I can accomplish this.
>> >> > >> >
>> >> > >> > Thanx.
>> >> > >>
>> >> >
>>


RE: SQL Developer Remote Access by v-terliu

v-terliu
Thu Jul 10 23:29:39 PDT 2008

Hello Customer,

Thank you for posting here.

According to your description, I understand that you want to make the
remote client only access your SQL server on SBS. If I have misunderstood
the problem, please don't hesitate to let me know.

Before we go any further, please let me know the following information so
that we can understand your situation more clearly.

1. Do you means VPN by "remote access"?

2. Do you have only one VPN client?

By default, the VPN clients could access all resource on SBS and internal.
If you want to make the VPN clients only access SQL server on SBS. We need
to create deny rules to block the other traffic.

If all answers are yes for the 2 questions above, I suggest you perform the
following steps:

Create 2 deny rules to block the traffic between VPN clients and LAN except
SQL server:

Rule 1:

Please open the ISA management console, navigate to Firewall Policy, right
click "Firewall Policy" and click New->Access Rule, then create a new
access rule as following:

Rule name: block all to internal and external

Rule Action: Deny

Protocols: All Outbound traffic except Microsoft SQL (TCP) and Microsoft
SQL (UDP)

Sources: VPN clients

Destination: Local Host

User Sets: All Users

Then move this rule above to "SBS Protected Networks Access Rules" and
click Apply to save all the settings.

Rule 2:

Please open the ISA management console, navigate to Firewall Policy, right
click "Firewall Policy" and click New->Access Rule, then create a new
access rule as following:

Rule name: block all except SQL server to local host

Rule Action: Deny

Protocols: All Outbound traffic

Sources: VPN clients

Destination: External and Internal

User Sets: All Users

Then move this rule above to "SBS Protected Networks Access Rules" and
click Apply to save all the settings.

Note: The VPN clients get IP from DHCP on SBS, not fix IP, so we unable to
only block certain VPN client.

I appreciate your time and look forward to hearing from you.

Thanks and have a nice day!

Best regards,

Terence Liu (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: SQL Developer Remote Access
>thread-index: AcjixJplJkUmtWTXTH28Cu5idSk+xg==
>X-WBNR-Posting-Host: 207.46.19.168
>From: =?Utf-8?B?TUY=?= <MF@discussions.microsoft.com>
>Subject: SQL Developer Remote Access
>Date: Thu, 10 Jul 2008 12:39:01 -0700
>Lines: 8
>Message-ID: <97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
>Newsgroups: microsoft.public.windows.server.sbs
>Path: TK2MSFTNGHUB02.phx.gbl
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:114796
>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hello All,
>
>I am trying to provide remote access "ONLY" to SQL server on our SBS 2003
>Premium ASAP so he can access only SQL server for development purposes.
>
>Any Ideas how I can accomplish this.
>
>Thanx.
>


RE: SQL Developer Remote Access by MF

MF
Fri Jul 11 07:23:02 PDT 2008

Thanx for your response. Yes your understanding of the issue is correct. We
enabled VPN on the SBS and we use this for the remote office users for all
day work. If I need to provide access to a database for the developer via VPN
how is it possible to restrict him from accessing anything else at all on the
server? Or what other options are there besides VPN or can the deny rules be
applied to only the developer? Just so you know, ISA server is not installed
on this SBS server, we basically use the firewall on our router and I have
forwarded TCP port 1433 and UDP port 1434 to the SBS server.

Thanx.

"Terence Liu [MSFT]" wrote:

> Hello Customer,
>
> Thank you for posting here.
>
> According to your description, I understand that you want to make the
> remote client only access your SQL server on SBS. If I have misunderstood
> the problem, please don't hesitate to let me know.
>
> Before we go any further, please let me know the following information so
> that we can understand your situation more clearly.
>
> 1. Do you means VPN by "remote access"?
>
> 2. Do you have only one VPN client?
>
> By default, the VPN clients could access all resource on SBS and internal.
> If you want to make the VPN clients only access SQL server on SBS. We need
> to create deny rules to block the other traffic.
>
> If all answers are yes for the 2 questions above, I suggest you perform the
> following steps:
>
> Create 2 deny rules to block the traffic between VPN clients and LAN except
> SQL server:
>
> Rule 1:
>
> Please open the ISA management console, navigate to Firewall Policy, right
> click "Firewall Policy" and click New->Access Rule, then create a new
> access rule as following:
>
> Rule name: block all to internal and external
>
> Rule Action: Deny
>
> Protocols: All Outbound traffic except Microsoft SQL (TCP) and Microsoft
> SQL (UDP)
>
> Sources: VPN clients
>
> Destination: Local Host
>
> User Sets: All Users
>
> Then move this rule above to "SBS Protected Networks Access Rules" and
> click Apply to save all the settings.
>
> Rule 2:
>
> Please open the ISA management console, navigate to Firewall Policy, right
> click "Firewall Policy" and click New->Access Rule, then create a new
> access rule as following:
>
> Rule name: block all except SQL server to local host
>
> Rule Action: Deny
>
> Protocols: All Outbound traffic
>
> Sources: VPN clients
>
> Destination: External and Internal
>
> User Sets: All Users
>
> Then move this rule above to "SBS Protected Networks Access Rules" and
> click Apply to save all the settings.
>
> Note: The VPN clients get IP from DHCP on SBS, not fix IP, so we unable to
> only block certain VPN client.
>
> I appreciate your time and look forward to hearing from you.
>
> Thanks and have a nice day!
>
> Best regards,
>
> Terence Liu (MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> =====================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
> >Thread-Topic: SQL Developer Remote Access
> >thread-index: AcjixJplJkUmtWTXTH28Cu5idSk+xg==
> >X-WBNR-Posting-Host: 207.46.19.168
> >From: =?Utf-8?B?TUY=?= <MF@discussions.microsoft.com>
> >Subject: SQL Developer Remote Access
> >Date: Thu, 10 Jul 2008 12:39:01 -0700
> >Lines: 8
> >Message-ID: <97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
> >Newsgroups: microsoft.public.windows.server.sbs
> >Path: TK2MSFTNGHUB02.phx.gbl
> >Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:114796
> >NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >Hello All,
> >
> >I am trying to provide remote access "ONLY" to SQL server on our SBS 2003
> >Premium ASAP so he can access only SQL server for development purposes.
> >
> >Any Ideas how I can accomplish this.
> >
> >Thanx.
> >
>
>

RE: SQL Developer Remote Access by v-terliu

v-terliu
Sun Jul 13 19:48:01 PDT 2008

Hello Customer,

Thank you for your update.

You said you run the SBS 2003 premium. Why don't you install the ISA server
2004 on the SBS? If you do not install the ISA server 2004 on SBS, we
completely unable to control VPN client access after the VPN connection is
established. So we suggest you install the ISA server on SBS.

Even if you install the ISA server 2004 on SBS, the ISA unable to
distinguish between developer and non-developer. After you create the 2
deny rules in my previous reply, all VPN clients could only access SQL
server on SBS.

Please do not forward TCP port 1433 and UDP port 1434 from your router to
the SBS server, it is very dangerous for your SBS and SQL server.
Meanwhile, it will be very slow when you access SQL Server thru Internet.

I hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: SQL Developer Remote Access
>thread-index: AcjjYaBRs5qt/oWpQBmBrfmsyrZf8g==
>X-WBNR-Posting-Host: 65.55.21.8
>From: =?Utf-8?B?TUY=?= <MF@discussions.microsoft.com>
>References: <97892EC7-0488-4BFD-962D-E8911DE8324F@microsoft.com>
<z2VjA#x4IHA.1620@TK2MSFTNGHUB02.phx.gbl>
>Subject: RE: SQL Developer Remote Access
>Date: Fri, 11 Jul 2008 07:23:02 -0700
>Lines: 157
>Message-ID: <0BA001BF-C358-437C-9B12-F430AA89FB6E@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
>Newsgroups: microsoft.public.windows.server.sbs
>Path: TK2MSFTNGHUB02.phx.gbl
>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:114894
>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Thanx for your response. Yes your understanding of the issue is correct.
We
>enabled VPN on the SBS and we use this for the remote office users for all
>day work. If I need to provide access to a database for the developer via
VPN
>how is it possible to restrict him from accessing anything else at all on
the
>server? Or what other options are there besides VPN or can the deny rules
be
>applied to only the developer? Just so you know, ISA server is not
installed
>on this SBS server, we basically use the firewall on our router and I have
>forwarded TCP port 1433 and UDP port 1434 to the SBS server.
>
>Thanx.
>
>"Terence Liu [MSFT]" wrote:
>
>> Hello Customer,
>>
>> Thank you for posting here.
>>
>> According to your description, I understand that you want to make the
>> remote client only access your SQL server on SBS. If I have
misunderstood
>> the problem, please don't hesitate to let me know.
>>
>> Before we go any further, please let me know the following information
so
>> that we can understand your situation more clearly.
>>
>> 1. Do you means VPN by "remote access"?
>>
>> 2. Do you have only one VPN client?
>>
>> By default, the VPN clients could access all resource on SBS and
internal.
>> If you want to make the VPN clients only access SQL server on SBS. We
need
>> to create deny rules to block the other traffic.
>>
>> If all answers are yes for the 2 questions above, I suggest you perform
the
>> following steps:
>>
>> Create 2 deny rules to block the traffic between VPN clients and LAN
except
>> SQL server:
>>
>> Rule 1:
>>
>> Please open the ISA management console, navigate to Firewall Policy,
right
>> click "Firewall Policy" and click New->Access Rule, then create a new
>> access rule as following:
>>
>> Rule name: block all to internal and external
>>
>> Rule Action: Deny
>>
>> Protocols: All Outbound traffic except Microsoft SQL (TCP) and Microsoft
>> SQL (UDP)
>>
>> Sources: VPN clients
>>
>> Destination: Local Host
>>
>> User Sets: All Users
>>
>> Then move this rule above to "SBS Protected Networks Access Rules" and
>> click Apply to save all the settings.
>>
>> Rule 2:
>>
>> Please open the ISA management console, navigate to Firewall Policy,
right
>> click "Firewall Policy" and click New->Access Rule, then create a new
>> access rule as following:
>>
>> Rule name: block all except SQL server to local host
>>
>> Rule Action: Deny
>>
>> Protocols: All Outbound traffic
>>
>> Sources: VPN clients