Losing File Share after reboot

[Guest Brian]

I have a Windows 2003 network.

Server A has a network file share to "DATA" . Share rights are full

control, file rights are full control.

Server B runs a scheduled task to transfer info from \\serverA\DATA to a

local folder on Server B.

 

Whenever Server A gets rebooted, it loses the folder to "DATA".

Other folder shares are not affected. Just that one folder "DATA".

 

It is not the Mapped Drive problem from the Microsoft KB297684.

 

Any help appreciated.

[Guest Brian]

RE: Losing File Share after reboot

 

Sorry, meant to say...

 

Whenever Server A gets rebooted, it loses the folder share to "DATA".

 

"Brian" wrote:

> I have a Windows 2003 network.

> Server A has a network file share to "DATA" . Share rights are full

> control, file rights are full control.

> Server B runs a scheduled task to transfer info from \\serverA\DATA to a

> local folder on Server B.

>

> Whenever Server A gets rebooted, it loses the folder to "DATA".

> Other folder shares are not affected. Just that one folder "DATA".

>

> It is not the Mapped Drive problem from the Microsoft KB297684.

>

> Any help appreciated.

[Guest Gis Bun]

RE: Losing File Share after reboot

 

Unsure of a solution why this is happening but you can always use the admin

shares (i.e. \\serverA\c$\data and \\serverB\c$\data - substitute proper

drive lettering and path).

 

By some fluke, if you don't have the admin shares then there is a

possibility that it was disabled unintentially or (unlikely) that the PC is

infected with a virus. I've seen a virus that trashes the network settings

and disables the admin shares (and and user created shares).

 

"Brian" wrote:

> Sorry, meant to say...

>

> Whenever Server A gets rebooted, it loses the folder share to "DATA".

>

> "Brian" wrote:

>

> > I have a Windows 2003 network.

> > Server A has a network file share to "DATA" . Share rights are full

> > control, file rights are full control.

> > Server B runs a scheduled task to transfer info from \\serverA\DATA to a

> > local folder on Server B.

> >

> > Whenever Server A gets rebooted, it loses the folder to "DATA".

> > Other folder shares are not affected. Just that one folder "DATA".

> >

> > It is not the Mapped Drive problem from the Microsoft KB297684.

> >

> > Any help appreciated.

[Guest Pegasus \(MVP\)]

Re: Losing File Share after reboot

 

 

"Brian" <Brian@discussions.microsoft.com> wrote in message

news:2CECB403-0EB9-4F0D-A871-2465511B9A36@microsoft.com...

>I have a Windows 2003 network.

> Server A has a network file share to "DATA" . Share rights are full

> control, file rights are full control.

> Server B runs a scheduled task to transfer info from \\serverA\DATA to a

> local folder on Server B.

>

> Whenever Server A gets rebooted, it loses the folder to "DATA".

> Other folder shares are not affected. Just that one folder "DATA".

>

> It is not the Mapped Drive problem from the Microsoft KB297684.

>

> Any help appreciated.

 

Have a look in the registry. Shares are nothing other than a value defined

here:

hklm/system/currentcontrolset/services/lanmanserver/shares

- Does the value exist before the reboot?

- After the reboot?

- Can you protect it?

- Do you maybe have a startup task that deletes it at boot time?

[Guest Paul King]

Re: Losing File Share after reboot

 

Brian,

 

When you reboot the Windows 2003 server (Server A) does it remove the share

indicator icon on the directory itself?

 

Cheers

Paul.

 

"Brian" <Brian@discussions.microsoft.com> wrote in message

news:103CFB57-55C2-48FE-BB12-2E31CE456C1F@microsoft.com...

> Sorry, meant to say...

>

> Whenever Server A gets rebooted, it loses the folder share to "DATA".

>

> "Brian" wrote:

>

>> I have a Windows 2003 network.

>> Server A has a network file share to "DATA" . Share rights are full

>> control, file rights are full control.

>> Server B runs a scheduled task to transfer info from \\serverA\DATA to a

>> local folder on Server B.

>>

>> Whenever Server A gets rebooted, it loses the folder to "DATA".

>> Other folder shares are not affected. Just that one folder "DATA".

>>

>> It is not the Mapped Drive problem from the Microsoft KB297684.

>>

>> Any help appreciated.