> Hello--
>
> We have some shared folders on external hard drives connected to PCs
> running WXP that we use to store archived data onto. These PCs are on
> different subnets and accessed remotely via an MPLS WAN.
>
> There is a server running W2K3 in our network that has a scheduled
> task to drop data into the shared folders on these remote computers
> periodically. It has done this task for over a year with no issues.
>
> Recently we replaced the server that is scheduled to drop the data
> into the remote shares and now it cannot access the shares. In fact,
> no machine in our network can access the shares any longer. I will
> post the error we are getting below, but I wanted to mention that
> there is plenty of storage space, and permissions are not the issue.
> As a troubleshooting effort, we unshared the folders, rebooted the PCs
> and then shared the folders again with the appropriate permissions.
>
> Again, the problem started when we replaced a server in our network
> but made no changes to the PC's where the shared folders are hosted.
> Here is the error we get:
>
> "\\server\share is not accessible. You might not have permission to
> use this network resource. Contact the administrator of this server to
> find out if you have access permissions. Not enough server storage is
> available to process this command."
>

"Meinolf Weber" wrote:

> Hello razor,
>
> What happens if you use \\ipaddress\share ? Did you check DNS settings on
> the new machine and also that it is registered in your DNS server correctly?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
>
> > Hello--
> >
> > We have some shared folders on external hard drives connected to PCs
> > running WXP that we use to store archived data onto. These PCs are on
> > different subnets and accessed remotely via an MPLS WAN.
> >
> > There is a server running W2K3 in our network that has a scheduled
> > task to drop data into the shared folders on these remote computers
> > periodically. It has done this task for over a year with no issues.
> >
> > Recently we replaced the server that is scheduled to drop the data
> > into the remote shares and now it cannot access the shares. In fact,
> > no machine in our network can access the shares any longer. I will
> > post the error we are getting below, but I wanted to mention that
> > there is plenty of storage space, and permissions are not the issue.
> > As a troubleshooting effort, we unshared the folders, rebooted the PCs
> > and then shared the folders again with the appropriate permissions.
> >
> > Again, the problem started when we replaced a server in our network
> > but made no changes to the PC's where the shared folders are hosted.
> > Here is the error we get:
> >
> > "\\server\share is not accessible. You might not have permission to
> > use this network resource. Contact the administrator of this server to
> > find out if you have access permissions. Not enough server storage is
> > available to process this command."
> >
>
>
>

"razor" wrote:

> Hello--
>
> If I use the ip address the same thing happens. All of the shared resources
> open on the target PC, however when I try to open the shared folder, I get
> the error that I posted earlier.
>
> The DNS on the new server is correct and the DNS records for that machine
> are correct on our DNS server.
>
> There is one more observation that might help. I can open shares on the
> server from the remote PC's. So the shared permissions, etc are going from
> the PC to the server, but not the server to the PCs.
>
> Can you think of anything else this can be?
>
> Thanks,
>
> sd
>
>
>
> "Meinolf Weber" wrote:
>
> > Hello razor,
> >
> > What happens if you use \\ipaddress\share ? Did you check DNS settings on
> > the new machine and also that it is registered in your DNS server correctly?
> >
> > Best regards
> >
> > Meinolf Weber
> > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> > no rights.
> > ** Please do NOT email, only reply to Newsgroups
> > ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
> >
> > > Hello--
> > >
> > > We have some shared folders on external hard drives connected to PCs
> > > running WXP that we use to store archived data onto. These PCs are on
> > > different subnets and accessed remotely via an MPLS WAN.
> > >
> > > There is a server running W2K3 in our network that has a scheduled
> > > task to drop data into the shared folders on these remote computers
> > > periodically. It has done this task for over a year with no issues.
> > >
> > > Recently we replaced the server that is scheduled to drop the data
> > > into the remote shares and now it cannot access the shares. In fact,
> > > no machine in our network can access the shares any longer. I will
> > > post the error we are getting below, but I wanted to mention that
> > > there is plenty of storage space, and permissions are not the issue.
> > > As a troubleshooting effort, we unshared the folders, rebooted the PCs
> > > and then shared the folders again with the appropriate permissions.
> > >
> > > Again, the problem started when we replaced a server in our network
> > > but made no changes to the PC's where the shared folders are hosted.
> > > Here is the error we get:
> > >
> > > "\\server\share is not accessible. You might not have permission to
> > > use this network resource. Contact the administrator of this server to
> > > find out if you have access permissions. Not enough server storage is
> > > available to process this command."
> > >
> >
> >
> >

"Henrik" wrote:

> Are you 100% sure of that it's not any permissions you have forgot to set on
> the folder? Start with granting authenticated users full control and don't
> restrict the folder with NTFS permissions. If Authenticated users have full
> control on the shared folder every user whos authenticated to the domain
> will be able to reach the share. Try this and respond. Maby you are setting
> to tight NTFS permissions on the shared folder, just a guess.
> --
> Henrik
> MCSE - Windows Server 2003 + MCP
>
>
> "razor" wrote:
>
> > Hello--
> >
> > If I use the ip address the same thing happens. All of the shared resources
> > open on the target PC, however when I try to open the shared folder, I get
> > the error that I posted earlier.
> >
> > The DNS on the new server is correct and the DNS records for that machine
> > are correct on our DNS server.
> >
> > There is one more observation that might help. I can open shares on the
> > server from the remote PC's. So the shared permissions, etc are going from
> > the PC to the server, but not the server to the PCs.
> >
> > Can you think of anything else this can be?
> >
> > Thanks,
> >
> > sd
> >
> >
> >
> > "Meinolf Weber" wrote:
> >
> > > Hello razor,
> > >
> > > What happens if you use \\ipaddress\share ? Did you check DNS settings on
> > > the new machine and also that it is registered in your DNS server correctly?
> > >
> > > Best regards
> > >
> > > Meinolf Weber
> > > Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> > > no rights.
> > > ** Please do NOT email, only reply to Newsgroups
> > > ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm
> > >
> > > > Hello--
> > > >
> > > > We have some shared folders on external hard drives connected to PCs
> > > > running WXP that we use to store archived data onto. These PCs are on
> > > > different subnets and accessed remotely via an MPLS WAN.
> > > >
> > > > There is a server running W2K3 in our network that has a scheduled
> > > > task to drop data into the shared folders on these remote computers
> > > > periodically. It has done this task for over a year with no issues.
> > > >
> > > > Recently we replaced the server that is scheduled to drop the data
> > > > into the remote shares and now it cannot access the shares. In fact,
> > > > no machine in our network can access the shares any longer. I will
> > > > post the error we are getting below, but I wanted to mention that
> > > > there is plenty of storage space, and permissions are not the issue.
> > > > As a troubleshooting effort, we unshared the folders, rebooted the PCs
> > > > and then shared the folders again with the appropriate permissions.
> > > >
> > > > Again, the problem started when we replaced a server in our network
> > > > but made no changes to the PC's where the shared folders are hosted.
> > > > Here is the error we get:
> > > >
> > > > "\\server\share is not accessible. You might not have permission to
> > > > use this network resource. Contact the administrator of this server to
> > > > find out if you have access permissions. Not enough server storage is
> > > > available to process this command."
> > > >
> > >
> > >
> > >