I am running VL in my company which all join to a windows domain. Some time I use VNC and rdesktop to remote to my PC. But then I cannot VNC/rdesktop based on the PC name, can only use the IP. I know I can add the IP and the PC name in the resolv.conf to resolve it. But I got a lot of PC in my company, I cannot add in all the name in the resolv.conf. In windows I no need to worry to resolve the PC name, is there away to do that same in VL?

I had something similar when I used Vector at BioAust. I had the benefit of a small number of machines and being the site IT expert, so I was able to set my machine as the master resolution device. There should be something in the various SMB documentations that'll show you how to set that, and after I changed that, I was generally able to VNC by hostname.

Good luck - not being able to do this sort of thing generally erodes a company's confidence in linux-based solutions.

I had something similar when I used Vector at BioAust. I had the benefit of a small number of machines and being the site IT expert, so I was able to set my machine as the master resolution device. There should be something in the various SMB documentations that'll show you how to set that, and after I changed that, I was generally able to VNC by hostname.

Good luck - not being able to do this sort of thing generally erodes a company's confidence in linux-based solutions.

(this is not a question as i already have the solution)i wanted to post this because i have been searching the last three days for this problem in many forums and found many people having similar problems but never got the right answer.

the situation in short- i have set up samba correctly and my windows pcs and linux pcs can see each other in the windows (netbios) network- shared files are reachable and readable from every pc- every pc can ping each other using the ip address (ping 192.168.0.100)- from windows pcs: ping netbios names is working (ping lepton2 will ping the ip behind the name lepton2)- PROBLEM! from linux pcs: ping netbios names will result in "unknown host lepton2"

the most common answer to this problem is: hardcode the host names in the hosts file. sure, this will work, but not if the network is using dhcp.