SimpleSi Posted May 18, 2009 Posted May 18, 2009 (edited) I've had peculiar problem with a new teacher laptop that I set up to access my simple shared \\suitec01\classwork folder and print via the server to the school printers. It seems to setup OK and then I gave it to the teacher who said he couldn't print or access \\suitec01\classwork but could still access the internet. I tried it out and he was right - it didn't work - i tried various things and then noticed that it connecting to the network via wireless as well as wired (the single school wireless wasn't placed to serve this classroom so it was chance it could see a signal and connect) If I disabled the wireless or kept the wireless and removed the net cable - the problems accessing the server went away. During the fault finding - it was more peculiar as the machine could access other shares on the server (junior librarian shared folder for instance) - just not the one needed Anyway, since he'll be using the laptop wirelessy at home, I've just pulled the wired connection to "solve" the problem. It seems strange that this is the first time I've had this problem in my schools but maybe I've just been lucky up till now. Has anyone else had this type of problem and is there a way of managing it better? regards Simon Edited May 18, 2009 by SimpleSi changed to correct server name!
SimpleSi Posted May 18, 2009 Author Posted May 18, 2009 Did browsing via a FQDN work with both connected? Don't know how to do that I just use start-run and then type in \\suitec01\classwork when testing and have \\suitec01\classwork as a shortcut on the desktop for normal use. regards Simon
SimpleSi Posted May 18, 2009 Author Posted May 18, 2009 JFI FQDN is suitec01.broadoakserver.local. regards Simon
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