Be careful about sharing your system's passwords on these forums! They have been known to be spidered.......
There are three parts to this problem.
1) All of your Windows computers need to be in the same workgroup.
To check/remedy this, take a look at this Microsoft document: http://support.microsoft.com/kb/2950172) Ubuntu needs to be in the same workgroup as your Windows computers.
To remedy this, follow the steps outlined in post 5.3) Ubuntu is unable to resolve Windows hostnames by default.
To remedy this, follow these steps: http://ubuntuforums.org/showpost.php...50&postcount=4
Last edited by dmizer; April 27th, 2009 at 08:08 AM.
Last edited by dmizer; June 4th, 2009 at 12:20 AM.
I just finally fixed my windows file sharing problem, perhaps this might help.
Here's the bottom line for what ailed my system. I needed to setup static IP's (192.168.1.xxx for my router) instead of dhcp.
Next, I had to add these entries to my /etc/hosts file.
I have a small home local lan and so there's no nameserver running anywhere. This means that hostname vs. ip addresses were not available to the ubuntu system from the network - which would silently fail. I found nothing in any logs either (but might have missed something).
The sad thing is that it fooled me because the network gui would find all the computer names, but only one would work.
My windows boxes all seem to find each other easily, but my 9.04 Ubuntu would only see one of my windows computers. And I am still puzzled how it found that one - somewhere along the line something (not me, I swear) did actually add my first and only windows ip address and name to the hosts file. When I added the rest, it all worked. I must have added these to the windows hosts files long ago and forgot this was needed on my network.
It's a shame that ubuntu network gui shows these computer and knows their names - it figures out they are there but can't open them w/o the ip address and it can't translate the windows host name it sees somehow into the ip address.
Anyway, maybe this is your problem.
I hope in the future that ubuntu will be more forthcoming about network failures and at least log what the failure is. I had to figure it out by staring at sniffer dumps for days until I saw where it was not getting the info it wanted.
I did finally figure out what was occurring that requires the hosts table entries.
My ubuntu system would issue a netbios broadcast (6 times) and it would get no response. So, after that, it would contact my first dns server (I use the open one at 18.104.22.168) which did respond. In this case, I provide a single host name, e.g. "myhost" which it would turn into www.myhost.com and then return an IP address. Next, ubuntu would think, oh this is good, let's try to do a netbios tcp connection here, which would fail - since this is some system somewhere on the public internet. It tries this 3 times then finally gives up. Anyway, that's what I saw using a hub and a sniffer.
By putting these into the hosts file, ubuntu then did the same things, except it did not go to the public nameserver, but rather immediately sent the netbios connection to my local computer (the right one) and got a response.
Last edited by rocket777; June 13th, 2009 at 12:33 AM.