Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1402
  • Last Modified:

When mapping drives, intermittent 'The Specified Network Name is No Longer Available' messages displayed

I have several servers all set up with Cygwin scripts to mount a network-attached storage device and then run NTBackup.  This works fine accross the board with a couple of exceptions.  One server refuses to backup as it loses the mapped drive, presumably when I log off, but the script does not reconnect the drive.  This procedure is in place and working for many other servers, including two on the same subnet as the faulting server, as the NAS is on a seperate backbone subnet.

This is driving me mad, I can find no explanation as to why this may happen.  I have tried:
Checking FW logs for large volume of network traffic - not consistent with fault timing
Using command line to make mapped drive persistant - not helped
Deleted and reconnected mapped drive several times

I realise many people frown upon NTBackup, my thoughts are that it is good for what we require.  It is the rest of the operating system that is messing things up!

What would be great is some sort of command line diagnostics relating to what network shares the machine has cached, if available?

Any suggestions are much appreciated, thanks for the help
0
slands10
Asked:
slands10
  • 4
  • 3
1 Solution
 
CharliePete00Commented:
I'd try the following:

1.  Write a script that
        a.  Maps your drive
        b.  Backs up to the mapped drive
        c.  Disconnects the mapped drive
2.  Create a scheduled task that will execute the script under an account with appropriate permissions

Or try backing up directly to a share via UNC (\\Sever\Share\BackupFile.bkf) instead of a mapped drive (z:\BackupFile.bkf)

0
 
slands10Author Commented:
Hi CharliePete,
That is the very thing I have done, I am using Cygwin to mount the drive, execute NTBackup, and the dismount the drive.  For doing this, I am using the full UNC convention (\\server.domain.com\drive).  A scheduled task is then used to execute a batch file which calls the Cygwin script.
What may confuse the issue slightly is that the target server is a NAS terabyte drive, which is working fine with every other backup scheduled.  This means I have very few options to configure on the target server, so most of the configuration must be done on the server that is to get backed up.  Access to the NAS is through shared folders, the one in question is named \backups, and so my UNC looks like \\nas01.xx.xx-xx.com\backups.  This works on every attempt *except* when the scheduling task is executing, or very occasionally when trying to mount the drive manually.
I have been thoroughly researching this as I am almost at my wit's end.  A Possible reason I have for the particular message ("The Specified Network Name is No Longer Available") is heavy network traffic, but on my network this should not be an issue at the time the script is executing.

Is there anyway to interrogate Windows 2K to see what mapped drives are in cache or such like?

Again, thanks for the help, I shall increase points for this q if that is more of an incentive to help out a poor, stressed individual!
0
 
Gareth GudgerCommented:
I wonder if it is a logon issue. Try resetting your credentials on the NTBackup job?
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
slands10Author Commented:
Hey, thanks, I'll give it a go, won't hurt.  We did notice that our NAS was configured with the wrong subnet, 255.255.255.0 rather than 255.255.240.0.  This didn't seam to affect most of the servers that were contacting the NAS to perform a scheduled backup, but it could have been some routing issue when most servers could find the NAS, but a few were unable to.
I'm still looking for suggestions, but I'm away for the night so hopefully tommorow I'll come in and we'll have a full round of backups completed without problem!

Thanks again for the input
0
 
CharliePete00Commented:
Now that we've eliminated some of the most obvious it looks like its time to roll up our sleaves and get to work ;-)

Let's start with the following:

1.  Start auditing authentication (logon) failures on the problem server
2.  Examine the event logs on the problem machine for errors corresponding with the times the backup job is attempted
3.  Logon to the problem machine with the same credentials (username, password) used to execute the backup job and attempt to execute the script manually.
4.  Replace references to the servername in UNCs in your script with IP addresses then attempt to execute the script manually and as a scheduled task
5.  Use a service wrapper (like Firedaemon) to execute your script as a service

Be sure to note and report any errors so we can help you resolve this
0
 
slands10Author Commented:
Hi again CharliePete,
Sorry, I'm really busy with a failed proxy server just now, but this looks to me as a plausible solution, I will give this a go and report back.  
5.  Use a service wrapper (like Firedaemon) to execute your script as a service

I am fairly confident the other suggestions do not apply to this situation or have been tried already, but I will still run through them.  Thanks again for the input
0
 
slands10Author Commented:
I'm really really sorry guys, I am a FUD.

I had my cygwin backup script looking in the wrong place for logfiles, so I was reporting failed every night.  I checked and we have a complete library of backups for this particular server.  Doh!

Again, really sorry for leading you all down a path to nowhere!

CharliePete, I award you points for your persistent help, many thanks.

Hope we have all learnt at least something from this experience...

Thanks again :-)
0
 
CharliePete00Commented:
Been there!

Hope you've your proxy taken care of.

Again, Good Luck!
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now