reboot everything .. that is what I had to do. Make sure that the Windows boxes are still granting network permissions
I haven't been on this forum very long but I think this is the first time I've seen anyone attempt to and fix this particular problem without suggesting to the user that he install winbind, edit a few other non relevant config files, and launch their own personal communications satellite in geosynchronous near-earth orbit.
I just have one request:
Don't you dare hide anything from us.PM me if you want the entire details as to what went wrong and what is the proper fix
You are welcome. I would say that you can mark the thread solved(and you have done so).
But..., You are not out of the woods just yet. We have proven that you basic problem involved name services. You have cured the immediate problem of DNS name resolution for maggie-pc by editing the /etc/hosts file. What happens when you add another host to the network? How will we prevent another host from using the IP address currently leased to maggie-pc?.
Actually the story has been told before. See here. In the past I have been accused (rightfully so, I must say) of providing too much information.
I just have one request:
Don't you dare hide anything from us.
You bring us tantalizingly close to the answer but then you stop. Perhaps you are telling us the answer and perhaps the answer is in the links you mentioned in your other post ( which I have not read ) but remember the rest of us are but mere mortals. In my particular case I have machines that had Windows and OSX preinstalled and linux machines. Except for throwing up a firewall or something overt , I can't make samba fail. It's been that way since I left SuSE 6. Everything works out of the box. If I'm doing something elegant ( and no one has ever accused me of that ) - if I'm doing anything at all - it's happening in my sleep. Others are not so fortunate ( or lucky ).
If you tell us the secret you'll have thousands of adoring fans and dispel one of the great Samba myths.
Last edited by Morbius1; July 28th, 2010 at 02:40 PM.
Solved, perhaps, but reading the original post is what led me here.
For others that arrive here with the dreaded
"Unable to mount location", read on.
What resolved my problem was turning off the firewall.
See post #14 >>
It was due to some updates a while ago. I never changed anything with my network since Lucid. Now I can see the WORKGROUP name again.