Hello Martin,
I've had some time to play with this. The code gksu... worked well. It
prompted me for my admin password, and I was able to make the necessary
changes, albeit not the ones recommended in the forum..
I used, the following instead:
name resolve order = lmhosts wins bcast host
I also
Hi Chris;
Glad it worked.
If you look at my post #18 above, you will see that name resolve order
= lmhosts wins bcast host is the order that I recommended. Assuming
you also removed the leading semicolon(;) from the line, then, that is
probably what did the trick for you.
Changing the
Hello Martin,
Thanks very much for the tip and the info. I will attempt this next time I
get to my laptop. My desktop is still a windoze machine.. :) I'll be
watching more in the forums.
Regards,
Chris
On Sat, Jul 25, 2009 at 5:38 PM, Martin G Miller mgmil...@optonline.netwrote:
When trying to
Hello,
I am a NEWBIE to the world of linux and ubuntu. Just installed ubuntu 9.04 a
few days ago and attached this laptop to my windows network. I get this same
error, even though my shares are turned on in my windows xp pro(sp3) machines.
I want to make the change as shown above to my
When trying to edit OS configuration files, you need to have root privileges.
The command to use in this case is:
gksu gedit /etc/samba/smb.conf
It will ask you for your password, just use the same password you use
when you log into Ubuntu.
For most help on these types of questions, you should
No, it usually slows down to do broadcast resolution (since you
basically have to wait for some timeout to decide that nobody has the
requested address), that's why it's tried last by default.
So solution for you is to change the resolve order in smb.conf. The
other solution is to set up
The smb.conf resolve order change is one of the first things I have to
do on new installs, so that is a work around for me. The fact that it
returns the wrong ip address on a ping command is something that I am
interested in. I tried the same tests at my office in another town and
it behaves
I found an interesting link here:
http://ubuntuforums.org/showthread.php?t=826938
They edited both smb.conf ( name resolve order = lmhosts bcast wins host)
Notice this resolve order is different than the one I am using. They also
modified nsswitch.conf (hosts:files dns wins) to get name
host unknown is the expected result to ping server since none of
your NSS backends knows about your server to translate it to IP.
That's what allows bcast to take over in your name resolve order and
successfully find the share.
Glad there was some opt-out, dns redirection is a real PITA.
--
@Martin: If ping any name fails, I wonder if the DNS redirection opt-
out has somehow effectively opted out of *all* DNS resolution? That
could explain why ping yahoo.com (for example) now fails. Can you still
browse the web, deal with email, etc as normal once opted out from the
DNS
What had stopped working was ping any local machine name. ping
yahoo.com worked fine.
What I have as of now is:
1) DNS redirection is turned off
2) smb.conf set to: (name resolve order = lmhosts wins bcast host)
3) nsswitch.conf set to: (hosts: files dns wins)
It took a restart to get
Apparently this is the (successful) smbclient output you get once you edited
the smb.conf file so that bcast is tried before host. I need the smbclient
trace for a failure case... Could you restore the original smb.conf file (the
one that fails) temporarily and regenerate/attach the resulting
So it seems that local access (tux-tux) is working correctly. Could you
try to access tux with smbclient from another machine (or access another
machine from tux) and send the corresponding smbclient log ? (using the
original, failing name resolve order set on the client, please)
Also could you
I set the smb.conf back to the default and here is the output of your 2
commands. These 2 commands take a while as it seems to time out after a
bit. If I run them with my modified smb.conf, they execute instantly
and show a lot of info on my network, with no apparent error messages.
Could you
The problem is apparently in your DNS resolution. Basically the master
browser says that UPSTAIRS exists. But when you browse it tries to
resolve UPSTAIRS to an IP address...
With the default resolve order, it tries DNS resolution before
broadcast. For some reason (I suspect a DNS that answers
ping upstairs does indeed try to resolve 67.63.55.3. This IP address is
nowhere in my network. ping does resolve it, but it takes about 23
ms. I have no idea why this should be. I have the exact same problem
on 2 different networks in 2 different towns using different brands of
routers. They
One last thought. If the default resolve order is using DNS before
broadcast, doesn't that slow down local network browsing? Since this
may turn out to be an ISP problem on my end, wouldn't it make sense to
change the default resolve order so it looks at the local network before
trying DNS?
I guess something changed in your network (or DNS settings) in September
of 2008, that makes your host resolution fail. Like switching to a
smart DNS server like OpenDNS...
Could you run the following command on one of your share-containing servers:
smbclient -d 4 -N -L //servername
and attach
Here is the requested output. This machine has the changed smb.conf
file and is both a samba server and also accesses shares over the
network.
** Attachment added: smbclient.txt
http://launchpadlibrarian.net/26682205/smbclient.txt
--
cannot browse samba shares without editing smb.conf
19 matches
Mail list logo
