This problem is still unsolved.
The host names of windows PCs are not visible to Linux programs with a regular
installation of Samba,
i.e. from Linux 'ping win_pc' does not work, but from windows 'ping linux_pc'
does work.
Also, 'nmblookup win_pc' works, while 'nslookup win_pc' does not work.
+1 ...this is an aggravating manual step every time I setup a new
ubuntu machine among a myriad of windows boxes. If we are going to
supplant the dominant OS, we have to be able to interact with it as
seamlessly as possible.
--
cannot resolve windows host name
https://bugs.launchpad.net/bugs/27
I agree that resolving windows names should happen by default (and while
outside the scope of this bug, 2 fresh ubuntu installs on the same LAN
should really also resolve each others names).
--
cannot resolve windows host name
https://bugs.launchpad.net/bugs/270395
You received this bug notificat
Geez. I agree. This should be fixed. Thanks to the reporter of this, and the
supplied fix.
But as the reporter said, I can't believe this is not considered to be
necessary to be made default for ubuntu. If Ubuntu is to 'just work', users
will want this already in place.
--
cannot resolve wind
Thanks Steve, I was not aware of the options.
So far winbind appears to be working good on my LAN...and until it works
do not fix it :)
--
cannot resolve windows host name
https://bugs.launchpad.net/bugs/270395
You received this bug notification because you are a member of Ubuntu
Server Team, wh
On Sat, Mar 14, 2009 at 09:39:36PM -, clovepower wrote:
> Are you suggesting that to have my Ubuntu laptop to connect to my
> Windows desktop on my 3 PC LAN, I've to setup an internal DNS server?
If you need to access your Windows PCs across the network for services other
than Windows fileshar
Actually if I go to Windows and do
ping
it works, and if I do
ping
it works too.
IMHO I think that most, if not all, Ubuntu users will sooner or later
plug their laptop into a LAN and they will expect to see other PCs,
hence this bug somehow will need to be addressed either fixing winbind
o
This is because using 'ping ' attempts to look up a host using
DNS. Using 'smb:///' uses lmhosts. If you were to go to Windows
and type 'ping ' it would fail the same way.
--
cannot resolve windows host name
https://bugs.launchpad.net/bugs/270395
You received this bug notification because you a
This is confirmed with
Ubuntu Jaunty alpha5 AMD64
samba 2:3.3.0-3ubuntu2
and no, I do not have any DNS server on my LAN.
I cannot try the above fix because Synaptic fails when installing
winbind (404 file not found), but still I'm not able to do:
ping
Notice that if I open Nautilis to smb://
Just to be clear.
Are you suggesting that to have my Ubuntu laptop to connect to my
Windows desktop on my 3 PC LAN, I've to setup an internal DNS server?
Or do I miss something?
--
cannot resolve windows host name
https://bugs.launchpad.net/bugs/270395
You received this bug notification because
The description in this bug report is complete; it is a request to
enable the WINS NSS module by default.
However, I'm going to have to mark this bug 'wontfix', because the
nss_wins module isn't mature enough to enable it by default, and using
it can cause recursion problems for apps in a variety
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Also, could you let
us know wheth
** Changed in: samba (Ubuntu)
Sourcepackagename: None => samba
--
cannot resolve windows host name
https://bugs.launchpad.net/bugs/270395
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
13 matches
Mail list logo