Network Drive Dropping

[FN-GM]

Hi,

On one of my servers the network drive mapped to it keeps dropping. I get the attached error. The only way to cure it is to reboot the server.

Nothing at all in the event log.

Does anyone have any ideas why please?

Thanks

[jamesfed]

Is it only that one networked drive and are any other servers/pcs having problems getting to that networked drive?

Also try pinging the server that drive is hosted on from the server that you get that error message on - long waits for responses could show problems with network cabling/drivers.

[mac_shinobi]

vbs that is mapping at logon or startup script or what exactly ?

Think the only time I had mine repeatedly drop was when I was using the wrong method to make the vbs map the network path ( cant remember which way around ) ie using startup instead of login or visa versa

[FN-GM]

Is it only that one networked drive and are any other servers/pcs having problems getting to that networked drive?

Also try pinging the server that drive is hosted on from the server that you get that error message on - long waits for responses could show problems with network cabling/drivers.

Only share on the server. I can ping it no problem when i get the issue.

vbs that is mapping at logon or startup script or what exactly ?

Think the only time I had mine repeatedly drop was when I was using the wrong method to make the vbs map the network path ( cant remember which way around ) ie using startup instead of login or visa versa

Its mapping through group policy preferences.

[Steve21]

Is it a new drive at all?

Might be worth trying to drop and readd it from nbtstat , in case it's confused as such

nbtstat -RR, then nbtstat -R

(Disclaimer, As always, be careful and preferably have backup incase Never know when it may decide not to readd it at all!)

Steve

[FN-GM]

I managed to sort it. The server is a new setup, when the guys come in to set it up they disabled IP V6 ont he network card. I enabled that again and the problems have gone away. Seems abit unusual though..

[mac_shinobi]

Clearly not the same situation as yourself but did find this :

Unable to map a network drive (Network Steve Forum)

I had posted this to some friends elsewhere, and here is the solution that worked for me. Set the Local Security Policy > Local Policy > Security Options > Network security: LAN Manager authentication level ... to ... Send LM & NTLM I have previously used
the setting of "Send LM & NTLM - use NTML2 session security if negotiated". This did not work for me. The "Send LM & NTLM" worked immediately. I began to see my network drives, both on and off of VPN. Hopefully this will save others the frustration.

Think that is with regards to windows 7 clients, can't see a mention of Server OS

[FN-GM]

Spoke too soon, it went off again.

@mac_shinobi that shouldnt matter as i have W7 clients

Anyone else got any thoughts please?

[kmount]

1 nic in the box?

Tried via IP when it's failed to rule out dns?
(arp happy? (compare arp when it's happy and working to arp when it's not for the same IP))

[mac_shinobi]

Spoke too soon, it went off again.

@mac_shinobi that shouldnt matter as i have W7 clients

Anyone else got any thoughts please?

Not used GPP to push out network drives / etc but can you not set them to be persistant via GPP or something like that. Also as KMount suggests, try using IP address of server instead of the hostname of the server so it does not rely on dns resolution.

Just wondering - its not to do with windows firewall and I presume you dont have any other software firewalls on the clients ?

Also all services on the client are running ie dhcp, dns, netbios helper etc etc and win 7 clients are getting the correct network info ie ip address, subnet mask, gateway, dns etc and if you take one off the domain and put it back on does that fix it for a bit ?

[FN-GM]

I can confirm its not a DNS issue. The server is a virtual server and has 1 nic assigned.

Thanks

[kmount]

I can confirm its not a DNS issue. The server is a virtual server and has 1 nic assigned.

Thanks

So are you saying when it's not working IP doesn't work either?

[FN-GM]

So are you saying when it's not working IP doesn't work either?

Yes that is correct.

[mac_shinobi]

Yes that is correct.

Can you ping the actual server that the Virtual server resides on when you are unable to ping the virtual server ?

Also what are you using for the virtual server ie ESXI, VMWARE etc etc

[kmount]

I'll assume you have confirmed you can still talk to the box via RDP or something at that time to rule out a true network problem (I wouldn't trust ping because if it's arp it might still be something "alive" that has stolen the IP).

ie, by RDP you can verify the box you're talking to is the box you want to be talking to.

Otherwise it might be worth trashing the arp table and then trying to reconnect, I've seen random shenanigans with shares when people have had poisoned arp tables.