name lookup

[Jeff Allain]

I believe my problem to be with vmware. I have a samba server setup on my
Fedora Core 2 box, and I am running a laptop with Fedora installed on it
as well. I installed win2k in Vmware on the laptop and when I use my
internal nic with bridged networking, everything works fine. I want to use
my wireless, so I had to change to NAT. This is where my problem comes in.
I can see my samba sever, but no shares from the win2k guest. I can run
the command nbtstat -a (server name) and it fails. I run the same command
by IP address and it works fine. I don't want to set up static IP's, so my
basic question is this. Why does it work ok using bridged networking and
eth0, but not wireless using NAT and ath0? It seems that the name
resolving does not work with NAT, or am I being led astray? By the way,
the guest can browse the shares from the samba server running on the
laptop, but not the main samba server running on my main machine. I have
disabled samba on the laptop and it makes no difference. Any help would be
appreciated.

Jeff Allain

[RobD]

The file /etc/resolv.conf (same as the one under sysconfig) contains the
info needed for name resolution. The "search" entry specifies the domain
search order, and the "nameserver" entries specify the IP addresses of the
name servers. More than likely you will see the "search" entry pointing to
localdomain and a name server pointing to vmnet8.

I had the same problem initially with dhcp and NAT. What I did to fix it is
add the name servers' IP addresses to vmware (edit Network Settings, select
NAT tab, edit vmnet8 - DNS..., and add IP addresses). This tells vmware to
go to your DNS servers for name resolution. When I added the domain search
order to linux (so I wouldn't have to use fully qualified domain names), the
dhclient-script kept resetting the "search" entry to localdomain on
restarts. I had to manually add "SEARCH=svr1.com svr2.com ..." to the top
of the script. This finally fixed name resolution with dhcp and NAT.

- Robert -

Post by Jeff Allain
I believe my problem to be with vmware. I have a samba server setup on my
Fedora Core 2 box, and I am running a laptop with Fedora installed on it
as well. I installed win2k in Vmware on the laptop and when I use my
internal nic with bridged networking, everything works fine. I want to use
my wireless, so I had to change to NAT. This is where my problem comes in.
I can see my samba sever, but no shares from the win2k guest. I can run
the command nbtstat -a (server name) and it fails. I run the same command
by IP address and it works fine. I don't want to set up static IP's, so my
basic question is this. Why does it work ok using bridged networking and
eth0, but not wireless using NAT and ath0? It seems that the name
resolving does not work with NAT, or am I being led astray? By the way,
the guest can browse the shares from the samba server running on the
laptop, but not the main samba server running on my main machine. I have
disabled samba on the laptop and it makes no difference. Any help would be
appreciated.
Jeff Allain