Can't get groups to work

Hi,
1. I have an Access ADP on SQL2000, uaing Windows users and groups..
2. Individual users with granted permissions work OK.
3. However, if I drop the individual users and try to uses the Windows
groups which contain them with same permissions granted, the app cannot make
connection.
4. Have revoked logins, re-added logins, database grants, and permissions,
but to no avail.
Any suggestions on what to look for?
Thanks.
AlanCan you make successfull connections from Query Analyser or OSQL.exe based
upon the group ?
Is the group a local group or domain based group?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks for your reply.
1. I can't connect with query analyzer, logging on to users's machine with
user's login but only his group login and group database access existing in
SQLServer.
2. User's group is a Universal domain group.
Using SQL@.000.
Useer: WinXP
OS: Win2000Server
DB Machine: Win2000 Server.
Regards,
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0WvCdgfxEHA.3640@.cpmsftngxa10.phx.gbl...
> Can you make successfull connections from Query Analyser or OSQL.exe based
> upon the group ?
> Is the group a local group or domain based group?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Ah. The problem may be the Universal Group.. There was a fix for this. Try
this update.
825042 FIX: SQL Server Jobs That Are Owned by Non-sysadmin Users May Not
Start
http://support.microsoft.com/?id=825042
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks for your reply.
This sounds like it applies to jobs only, not regular database accesss. Do
you know if it applies to database access as well.
I'd like to avoid hotfixes on client's computers as well, plus I don't know
if they have installed required Win2000 SP4.
Thanks.
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:7AkfzfpxEHA.768@.cpmsftngxa10.phx.gbl...
> Ah. The problem may be the Universal Group.. There was a fix for this.
Try
> this update.
> 825042 FIX: SQL Server Jobs That Are Owned by Non-sysadmin Users May Not
> Start
> http://support.microsoft.com/?id=825042
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||Its' been some time since I did testing, but I don't think we enumerate
Universal Groups only Domain Global Groups.
Try;
xp_logininf groupname
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0mIdcZrxEHA.3984@.cpmsftngxa10.phx.gbl...
> Its' been some time since I did testing, but I don't think we enumerate
> Universal Groups only Domain Global Groups.
> Try;
> xp_logininf groupname
Kevin,
Thanks again for your reply.
I've asked net admin to recreate groups as global, not universal.
In meantime, I've put results of xp_logininfo below.
1. xp_login 'GroupAccountName', 'members': properly displays list of members
2. xp_login 'GroupMemberAccountName', 'all': gives NULL RECORD!!
3. If, as a test, I add the GroupMemberAccountName to SQL logins as new
separate login IndividualUserName and do
xp_login 'IndividualUserName', 'all' :
then displays individual user's record, but no additional record for group
path.
CONCLUSION?
--
Does above mean that somewhere no connection is being made in SQLServer
between the group and the individual member?
BOL on xp_logininfo: If account_name is a valid Windows NT account but that
account does not have permission to access SQL Server, an empty result set
is returned.
Thanks very much.
Alan|||I know that Domain Local Groups won't work correctly for jobs and I
couldn't remember the results with Universal Groups.
Another question is , Is SQL Server in the same Domain that the users
groups are defined in?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
It's in a separate domain.
Alan
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:0Jw0SF1xEHA.3984@.cpmsftngxa10.phx.gbl...
> I know that Domain Local Groups won't work correctly for jobs and I
> couldn't remember the results with Universal Groups.
> Another question is , Is SQL Server in the same Domain that the users
> groups are defined in?
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Can't connect to SQL Server 2005 over VPN

Hi - if anyone can point me the the right direction it would be very
much appreciated. I have searched the groups but haven't sorted this
out yet.
I am trying to connect to a SQL Server 2005 database over a VPN and am
not having any success. Perhaps there are some other tests that can be
recommended to me to narrow down the problem.
The Server (at the office): Windows 2003 R2 with SQL Server 2005 (this
server is not a domain controller)
The Client (at home): Windows XP Pro
VPN: I can connect via the VPN just fine it would seem (for example, I
can browse shared folders on the server)
My Test: As my ultimate goal is to make a ODBC connection to the
server DB, I have been attempting to make an ODBC DSN with the ODBC
Data Source Administrator - it always fails (error is: SQL Server does
not exist of access denied).
Other notes:
- I can successfully connect to the SQL Server database from another
computer that is at the office
- At home, if I ping the server by name, the proper 'remote' IP
address gets returned, however I get 'request timed out' instead of
the 'reply from...'
- At home, In the ODBC Administrator setup, it automatically picks up
the remote server (by IP and by name) in the 'Server' drop down list.
- As far as I know, I have set SQL Server to accept remote connections
Suggestions very much appreciated !
I'm not an expert on how vpns are set up, but my guess is that there is a
firewall that is allowing traffic through the ports used by the vpn, but is
blocking your access to port 1433 which is what the database uses.
MG
"jan.mazing@.gmail.com" wrote:

> Hi - if anyone can point me the the right direction it would be very
> much appreciated. I have searched the groups but haven't sorted this
> out yet.
> I am trying to connect to a SQL Server 2005 database over a VPN and am
> not having any success. Perhaps there are some other tests that can be
> recommended to me to narrow down the problem.
> The Server (at the office): Windows 2003 R2 with SQL Server 2005 (this
> server is not a domain controller)
> The Client (at home): Windows XP Pro
> VPN: I can connect via the VPN just fine it would seem (for example, I
> can browse shared folders on the server)
> My Test: As my ultimate goal is to make a ODBC connection to the
> server DB, I have been attempting to make an ODBC DSN with the ODBC
> Data Source Administrator - it always fails (error is: SQL Server does
> not exist of access denied).
> Other notes:
> - I can successfully connect to the SQL Server database from another
> computer that is at the office
> - At home, if I ping the server by name, the proper 'remote' IP
> address gets returned, however I get 'request timed out' instead of
> the 'reply from...'
> - At home, In the ODBC Administrator setup, it automatically picks up
> the remote server (by IP and by name) in the 'Server' drop down list.
> - As far as I know, I have set SQL Server to accept remote connections
> Suggestions very much appreciated !
>
|||Can anyone help? Is there another group I should post this in?
Thanks

Can't connect to SQL Server 2005 over VPN

Hi - if anyone can point me the the right direction it would be very
much appreciated. I have searched the groups but haven't sorted this
out yet.
I am trying to connect to a SQL Server 2005 database over a VPN and am
not having any success. Perhaps there are some other tests that can be
recommended to me to narrow down the problem.
The Server (at the office): Windows 2003 R2 with SQL Server 2005 (this
server is not a domain controller)
The Client (at home): Windows XP Pro
VPN: I can connect via the VPN just fine it would seem (for example, I
can browse shared folders on the server)
My Test: As my ultimate goal is to make a ODBC connection to the
server DB, I have been attempting to make an ODBC DSN with the ODBC
Data Source Administrator - it always fails (error is: SQL Server does
not exist of access denied).
Other notes:
- I can successfully connect to the SQL Server database from another
computer that is at the office
- At home, if I ping the server by name, the proper 'remote' IP
address gets returned, however I get 'request timed out' instead of
the 'reply from...'
- At home, In the ODBC Administrator setup, it automatically picks up
the remote server (by IP and by name) in the 'Server' drop down list.
- As far as I know, I have set SQL Server to accept remote connections
Suggestions very much appreciated !I'm not an expert on how vpns are set up, but my guess is that there is a
firewall that is allowing traffic through the ports used by the vpn, but is
blocking your access to port 1433 which is what the database uses.
--
MG
"jan.mazing@.gmail.com" wrote:
> Hi - if anyone can point me the the right direction it would be very
> much appreciated. I have searched the groups but haven't sorted this
> out yet.
> I am trying to connect to a SQL Server 2005 database over a VPN and am
> not having any success. Perhaps there are some other tests that can be
> recommended to me to narrow down the problem.
> The Server (at the office): Windows 2003 R2 with SQL Server 2005 (this
> server is not a domain controller)
> The Client (at home): Windows XP Pro
> VPN: I can connect via the VPN just fine it would seem (for example, I
> can browse shared folders on the server)
> My Test: As my ultimate goal is to make a ODBC connection to the
> server DB, I have been attempting to make an ODBC DSN with the ODBC
> Data Source Administrator - it always fails (error is: SQL Server does
> not exist of access denied).
> Other notes:
> - I can successfully connect to the SQL Server database from another
> computer that is at the office
> - At home, if I ping the server by name, the proper 'remote' IP
> address gets returned, however I get 'request timed out' instead of
> the 'reply from...'
> - At home, In the ODBC Administrator setup, it automatically picks up
> the remote server (by IP and by name) in the 'Server' drop down list.
> - As far as I know, I have set SQL Server to accept remote connections
> Suggestions very much appreciated !
>|||Can anyone help? Is there another group I should post this in?
Thanks:)

Can't connect to SQL Server 2005 over VPN

Hi - if anyone can point me the the right direction it would be very
much appreciated. I have searched the groups but haven't sorted this
out yet.
I am trying to connect to a SQL Server 2005 database over a VPN and am
not having any success. Perhaps there are some other tests that can be
recommended to me to narrow down the problem.
The Server (at the office): Windows 2003 R2 with SQL Server 2005 (this
server is not a domain controller)
The Client (at home): Windows XP Pro
VPN: I can connect via the VPN just fine it would seem (for example, I
can browse shared folders on the server)
My Test: As my ultimate goal is to make a ODBC connection to the
server DB, I have been attempting to make an ODBC DSN with the ODBC
Data Source Administrator - it always fails (error is: SQL Server does
not exist of access denied).
Other notes:
- I can successfully connect to the SQL Server database from another
computer that is at the office
- At home, if I ping the server by name, the proper 'remote' IP
address gets returned, however I get 'request timed out' instead of
the 'reply from...'
- At home, In the ODBC Administrator setup, it automatically picks up
the remote server (by IP and by name) in the 'Server' drop down list.
- As far as I know, I have set SQL Server to accept remote connections
Suggestions very much appreciated !I'm not an expert on how vpns are set up, but my guess is that there is a
firewall that is allowing traffic through the ports used by the vpn, but is
blocking your access to port 1433 which is what the database uses.
--
MG
"jan.mazing@.gmail.com" wrote:

> Hi - if anyone can point me the the right direction it would be very
> much appreciated. I have searched the groups but haven't sorted this
> out yet.
> I am trying to connect to a SQL Server 2005 database over a VPN and am
> not having any success. Perhaps there are some other tests that can be
> recommended to me to narrow down the problem.
> The Server (at the office): Windows 2003 R2 with SQL Server 2005 (this
> server is not a domain controller)
> The Client (at home): Windows XP Pro
> VPN: I can connect via the VPN just fine it would seem (for example, I
> can browse shared folders on the server)
> My Test: As my ultimate goal is to make a ODBC connection to the
> server DB, I have been attempting to make an ODBC DSN with the ODBC
> Data Source Administrator - it always fails (error is: SQL Server does
> not exist of access denied).
> Other notes:
> - I can successfully connect to the SQL Server database from another
> computer that is at the office
> - At home, if I ping the server by name, the proper 'remote' IP
> address gets returned, however I get 'request timed out' instead of
> the 'reply from...'
> - At home, In the ODBC Administrator setup, it automatically picks up
> the remote server (by IP and by name) in the 'Server' drop down list.
> - As far as I know, I have set SQL Server to accept remote connections
> Suggestions very much appreciated !
>|||Can anyone help? Is there another group I should post this in?
Thanks