tmcd35 Posted February 5, 2014 Posted February 5, 2014 Okay, a week or so back I started a BTRD thread because a teacher was moaning about what looked like a Windows Profile issue: http://www.edugeek.net/forums/behind-red-door/130835-perfect-roaming-profiles-2.html#post1118049 I've been able to look at the problem a little closer, and it appears to be randomly effecting machines just in that one room. If they log off, log back on - the problem is resolved. So, I'm thinking bandwidth/dropped packet issue on the local switch? Logged on to the switch and reset all port counters so I can make sense of whats going on. Hour and half later... Only the uplink port (#49, 1GBps fibre to core switch) is showing any dropped packets. So far it's dropped 79 out of 1.351 billion. No other ports showing any problems so far, no collisions and no other errors. Where do I go from here?
DMcCoy Posted February 5, 2014 Posted February 5, 2014 Do you have slow profile detection disabled? That's a very low number of dropped packets anyway, although you might still get a profile timeout if everyone logs in a once. 1
tmcd35 Posted February 5, 2014 Author Posted February 5, 2014 Do you have slow profile detection disabled? No that's currently not configured. Have noticed another setting "Control slow network connection timeout for user profiles" that might be worth altering? That's a very low number of dropped packets anyway, although you might still get a profile timeout if everyone logs in a once. Yeah, that's what got me. All evidence suggests slow network/dropped packets - but the switch so far isn't agreeing.
DMcCoy Posted February 5, 2014 Posted February 5, 2014 No that's currently not configured. Have noticed another setting "Control slow network connection timeout for user profiles" that might be worth altering? Yeah, that's what got me. All evidence suggests slow network/dropped packets - but the switch so far isn't agreeing. Don't forget that smb has little in the way of priority for queued requests, there could be a delay from the server end when responding that causes a time out (requests not getting a timely response is the cause of things like delayed write failed with cheaper NAS etc). It's worth playing with the timeouts and setting slow link detection to 0 for wired clients to disable it.
tmcd35 Posted February 5, 2014 Author Posted February 5, 2014 Yeah, if it was server side I'd expect the same problems to appear in other rooms. It's just that one location. I'll enable the "diable detection of slow network connections" and see if it has any effect. Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now