How can we help you today? How can we help you today?

Adding Netowrk Drives

First of all, thanks for a great product.
Been using V5 for 3 years now and it just works.

First thing I did was set up a scheduled backup of the local server.
Noticed that the browse folder selection dialog has changed slightly.
There is now an indication of the logged in user/credentials used to connect to netwrok drives.

Hoewever, all it displays is 'Logged in as user b>/b>'

I am logged in as a local user on the server (Windows 2003 R2 EE SP2)

It would also be good to be able to change the security context of the connections - I have occasionally needed to lock down servers for access by a controlled account

Thanks
Andy
andy hughes
0

Comments

6 comments

Sort by
  • RBA
    Hi Andy,

    Thanks for the great feedback! Good to hear that v5 has served you well.

    The "b>/b>" you see is probably due to the use of certain characters in the SQL Server username. This is just cosmetic, but is something we hope to address.

    In reality, hosts for Windows network shares won't accept SQL Server logins for authentication - only domain accounts or local accounts with identical username and password. The account which SQBCoreService.exe uses determines what you can see since this will be the process that handles the shipping of files across the network - not the account SQL Server uses (or the SQL login we report, if you're not using Windows authentication for the core service to SQL Server connection).

    So to get this to work you will need to change the login details of our core service to your controlled account. (Start... Run... "services.msc" find "SQL Backup Agent[instance name]"... Right click... Properties... Log on).

    If this doesn't work, please let me know.

    Many thanks

    Robin
    RBA
    0
  • Nigel Morse
    Hi Andy,

    What was the username you were using to log in to this server, and did it (as RBA suggests) have characters like < or > in the name?

    Thanks
    Nigel
    Nigel Morse
    0
  • andy hughes
    Nigel

    The local login was 'devuser'
    The servername was PV_LPDATA_01
    2 underscore characters in the name - nothing illegal or even uncommon in that.

    I'm logged in via remote desktop using this user, and a query session returns exactly those details when I retreived the value of SUSER_SNAME()

    Thanks
    Andy
    andy hughes
    0
  • Nigel Morse
    Thanks. We managed to reproduce it, but only by having a user called <> - and this then broke the HTML used to put the username in bold.

    not quite sure why it broke in your case, but I've put some proper HTML encoding round the username which hopefull should fix it for you as well for final release.
    Nigel Morse
    0
  • meklembl
    Just throwing in my two cents. As you say, I don't see anything wrong with the user or server names. Is there something within the domain name that could be causing a break in the HTML output?
    meklembl
    0
  • andy hughes
    Good point.

    I'd overlooked the fact that this server is on a separate subnet and is not a member of the main company domain. This is the reason for using a local login to connect

    It's part of a workgroup containing around 5 servers with the default name of 'WORKGROUP'.
    andy hughes
    0

Add comment

Please sign in to leave a comment.