New NAS. Intermittent Map connection

[Cymark]

Hi.

Just installed a new TS-453D. All seems to work ok, but a couple of our older machines (running as virtual machines inside Win10) are having problems with the map.

We can create the map \\192.xxx.xxx.xxx\folder_of-interest\ without any problem and the map will work.

5 minutes later when clicking on the map letter we get the "local device name is already in use" message. BUT if you click ok, try again, it will fail 3 times then on the 4th or 5th attempt it will connect and work as if nothing has happened.

Causing a bit of a problem, because the legacy machines are writing data back to the shared drive on the NAS and keep falling over because they don't have the human input option to keep trying the drive.

Has anyone seen in intermittent map problem before? Is there something that 'times out'? Any help would be hugely appreciated.

Thanks

Guy

[dolbyman]

define "older machines"

Win XP
Win98
Win 3.11

is it the first time these machines deal with network shares ?

[Cymark]

Sorry. Running Windows XP inside Hyper-V.

The machines have been working up to this point using older Buffalo Terrastation NAS units.

Thanks

Guy

[dolbyman]

So if it works eventually, I guess you do have SMB1 active on the NAS correct ?

[Cymark]

Yes, have SMBv1 turned on. (was a little surprised that it was already turned after setup)

Worked first time. And when it does work, you wouldn't notice anything was wrong. Then pause, not use the drive for a few minutes and the message appears if you try to access it.

At the moment I only have one legacy VM machine on and one Win10 machine on while I was setting it up.

[dolbyman]

Are you maybe running a mount script? (maybe even twice with delay)

I haven't fired up XP in a while (last time was as for a printserver for a 25 year old HP LFP, as there is no drivers anymore for anything beyond WinXp)

[Cymark]

Thanks for the reply.

At the moment, it isn't running any scripts. The connection is pretty basic. Login, the first time the machine comes up, to the NAS, normally ok. And the map has been working.

I think I am also getting the same problem with the Win10 machines, but over a much longer time frame.

I just stopped for a bit to eat, came back to file manager on the Win10 machine I had left open and it came up with the same message. But wouldn't clear when I kept retrying it.

But closed FM, reopened it and the MAP worked straight away.

Scratching my head with this one

[dolbyman]

Could be a hardware issue (NAS,Switch,etc)

Maybe open a ticket with QNAP

[Cymark]

Thanks, good idea.