Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
 Posted - 2002-11-14 : 11:44:17
|
| Hi, I have an interesting, albeit annoying, remote access problem:I'm trying to use the SQL Server 7.0 desktop edition software from home on my XP (Home version) machine to do light maintenance of our SQL server when I can't get to the office.At my previous job this was a breeze. Microsoft products across the board, Remote Access Service (RAS) for dial-up. Just dial-up, pass credentials, launch SQL Server client, register server sitting at work, and go.At my current job there is a second line of "defense" where dial-up is concerned. They use an ISP-like service that forces us to use a second account, in addition to our main network account. We dial-up to the network with this unique REMOTE account and then when we want to link to resources on the network we must pass our WIN 2K credentials. This works fine for shared directories and such, when I can get XP to prompt for new credentials, but not for the SQL Server 7.0 client at home. When I try to register the SQL Server sitting at work on my home machine via dial-up, the registration fails with a message similar to "Registration failed for user (Null)". The problem seems to arise because SQL Server 7.0 desktop edition does not prompt me for my credentials, but instead passes whatever credentials it finds on the XP machine to the network.I'm not sure how to fix this. I've been trying to get XP Home to allow me to log on to the XP machine with same username, password, and domain as I have at work in hopes that these credentials will be passed to SQL Server at the time of attempted registration. However, I have not been able to find a domain field on XP Home Edition logon box.I also wonder if there's a way to force the SQL Server 7.0 desktop edition software to prompt me for my domain\username\password credentials before it tries to register the server.Any help is appreciated.Thanks. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2002-11-14 : 12:23:08
|
| You should create an account on SQL Server that uses sql authentication instead of windows authentication. So when you are at home, you will use the sql account instead of the one that XP is passing to SQL Server. I have the same situation at my work with some developers. At work, they use their windows account. At home, they use their sql account. It works, but it's a little annoying as a DBA to have to maintain two accounts for certain people. |
 |
|
|
steelkilt
Constraint Violating Yak Guru
255 Posts |
Posted - 2002-11-14 : 14:15:44
|
| Great idea. I'll try it.thx |
|
|
|
|
|
|
|
|
SQL 7.0 desktop ed. over dialup won't authenticate