You should avoid administrative shares. You can secure things by naming
your share with a trailing $ sign (e.g. MyShare$) and then granting access
only to specific accounts - such as the SQL Server domain account.
--
Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com ..
[quoted text, click to view] "Paul" <Paul@discussions.microsoft.com> wrote in message
news:E41041B5-608C-4BB1-9387-52A7FD5DD518@microsoft.com...
Thanks Tom My mistake was that I was just using the share drive letter and
not the UNC. I am OK w/ using the default share (c$). Just not an actual
share people would see and get to.
[quoted text, click to view] "Tom Moreau" wrote:
> You'll need to use the full UNC name - and means using a share.
>
> --
> Tom
>
> ----------------------------------------------------
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
>
www.pinnaclepublishing.com > ..
> "Paul" <Paul@discussions.microsoft.com> wrote in message
> news:8C1B820D-4AD7-471C-BE22-D6AE694155FB@microsoft.com...
> OK ... maybe I am being dumb but for the life of me I cannot figure this
> out.
> I have two servers both running 2003 and SQL Server 2k. I need to backup
> a
> database across the network from server A to server B. I need to do this
> without creating a share on either server. I have tried mapping virtual
> drives, mapping to default network shares, I have added the SQL accounts
> into
> Windows, added the Windows accounts into SQL. I keep getting that the
> device
> is not present. I can get to the drive letter through DOS so I am fairly
> sure it is a permission issue in SQL.
>
> What am I missing?
>
> Paul
>
>
