Network Drives mapped don't mount properly on windows boot

[Toxic Waste]

Hi guys,

I'm having a bit of an odd problem and I was wondering if anyone else has had the same problem. I have 5 CIFS shares that I have mapped as network drive on my windows 10 machine. When I boot my computer and log in, the network drives are supposed to connect automatically.

This happens correctly for 2 of the CIFS shares. The other 3 show the red cross that they aren't connected. However, when I open the drive, they just connect like they should on startup and I don't have to enter credentials or anything like that.

Is this a problem that lies within my FreeNAS machine, or is it a Windows issue?

Any help is much appreciated!

 

[Jailer]

Sounds like they are trying to connect before the network adapter driver has finished loading. Happens to me occasionally, I wouldn't worry about it.

 

[Toxic Waste]

Sounds like they are trying to connect before the network adapter driver has finished loading. Happens to me occasionally, I wouldn't worry about it.

well I thought that first aswell, but how is it possible that 2 out of the 5 connect instantly, and the other ones even get a popup from windows saying he can't connect to them? It also doesn't happen occassionally, it's every time I boot that this happens

 

[Jailer]

well I thought that first aswell, but how is it possible that 2 out of the 5 connect instantly, and the other ones even get a popup from windows saying he can't connect to them? It also doesn't happen occassionally, it's every time I boot that this happens

Because Windows.

 

[Toxic Waste]

Because Windows.

That is probably part of the problem, the thing is that, before I used FreeNAS, I had a synology box, and it worked with more than 2 drives mapped on that machine, so there is some link with FreeNAS at some point, maybe I should try remapping them from scratch, but it didn't seem to work the first time I tried that.

Could it be some CIFS setting or something like that? Maximum allowed connections?

Edit: further researching this on internet, it might be a Windows problem like you said, I will try some workarounds tonight, thanks ! :)

 

[pirateghost]

It happens at work when connecting to Windows shares hosted on Windows servers. It's a Windows problem