Comments on: Access Linux Workstation by Hostname on a Windows Network http://www.terminally-incoherent.com/blog/2007/10/03/access-linux-workstation-by-hostname-on-a-windows-network/ Utterly random, incoherent and disjointed rants and ramblings... Sat, 10 Jan 2009 02:17:12 +0000 http://wordpress.org/?v=2.0.5 by: Mehdi Karamnejad http://www.terminally-incoherent.com/blog/2007/10/03/access-linux-workstation-by-hostname-on-a-windows-network/#comment-10506 Sun, 26 Oct 2008 18:24:41 +0000 http://www.terminally-incoherent.com/blog/2007/10/03/access-linux-workstation-by-hostname-on-a-windows-network/#comment-10506 [quote post="1984"]why would I take that hassle and install samba server just to be visible?[/quote] when u have a problem like mine! check this out there are over 100 windows stations on a network ,they are all one subnet and all work with netbios names! there is no dns server and if there is you are not authorised to use dns server,not for performance reasons you decide to migrate one of servers from windows to linux,from now on you have no name in those stupid windows stations! :D here this hint will blast! thanks man

why would I take that hassle and install samba server just to be visible?

when u have a problem like mine! check this out
there are over 100 windows stations on a network ,they are all one subnet and all work with netbios names! there is no dns server and if there is you are not authorised to use dns server,not for performance reasons you decide to migrate one of servers from windows to linux,from now on you have no name in those stupid windows stations! D here this hint will blast! thanks man

]]> by: Luke Maciak http://www.terminally-incoherent.com/blog/2007/10/03/access-linux-workstation-by-hostname-on-a-windows-network/#comment-6423 Thu, 04 Oct 2007 13:55:15 +0000 http://www.terminally-incoherent.com/blog/2007/10/03/access-linux-workstation-by-hostname-on-a-windows-network/#comment-6423 Thanks! I fixed it. Oh, and if you are working in primarily Windows network having samba around might be a good idea. If I want to I can set up samba shares and make it available. And I think smbfs depends on samba - and that's what I use to mount windows network shares on my machine. Thanks! I fixed it.

Oh, and if you are working in primarily Windows network having samba around might be a good idea. If I want to I can set up samba shares and make it available. And I think smbfs depends on samba - and that’s what I use to mount windows network shares on my machine.

]]> by: ths http://www.terminally-incoherent.com/blog/2007/10/03/access-linux-workstation-by-hostname-on-a-windows-network/#comment-6411 Thu, 04 Oct 2007 06:02:06 +0000 http://www.terminally-incoherent.com/blog/2007/10/03/access-linux-workstation-by-hostname-on-a-windows-network/#comment-6411 a minor typo: dhc_l_ient.conf why would I take that hassle and install samba server just to be visible? I'd rather add a DNS service and let DHCP/DNS take care of it all. Then WINS will resolve netbios names by querying DNS (assuming that netbios name equals DNS hostname). Samba will pick up changes to smb.conf after at most 1 minute or you can force a reload of smb.conf with kill -HUP (-1) to the parent smbd process (the one with ppid==1). a minor typo: dhc_l_ient.conf

why would I take that hassle and install samba server just to be visible? I’d rather add a DNS service and let DHCP/DNS take care of it all. Then WINS will resolve netbios names by querying DNS (assuming that netbios name equals DNS hostname).

Samba will pick up changes to smb.conf after at most 1 minute or you can force a reload of smb.conf with kill -HUP (-1) to the parent smbd process (the one with ppid==1).

]]>