I have a friend with an office in his house that has been using a box with win2k pro as an in-house file server for quite a while with literally zero problems. The h/w was updated a couple of years ago and it just keeps going fine - though I'll be replacing it with a Linux box in the future sometime for him. There is just him, a secretary & a part-time assistant, a total of 3 other PCs that share files via the server. I just replaced his desktop PC with a Linux box that also has a VM of his previous XP system for his specialised s/w to stay in use & most everything is fine, but... Samba refuses to play nice with the shared stuff on the win2k pro server. With or without credentials it will not gain access - though that box is visible to it, the logging in fails every time such that he has no more direct access at his PC to his own files in the host OS. What is really puzzling about this happened when the VM of XP fired up & already had ALL of his shares from the server active & perfectly accessible with zero hesitation. All the network protocols are active on the win2k box & I've tried every trick I have been able to find without any success. I know that win2k in the non-server versions has sharing limitations hard coded into it. I am hoping that someone else here has run into this problem & has some sort of a workaround for it, like maybe some sort of file sharing app that works around it, or a way to sort of unlock the limits ?? Simply replacing it would be my best option, I know - but sadly ATM my personal problem is in getting there as I am over 100 miles away with no car at present, so I need to do what I can via remote, if possible. Thanks for any helpful pointers !!