>> This is a problem. I don't know of any Linksys router that acts as a DNS server. > It does act as DNS for my Windows machines.
They have the router set as the only DNS.
A cable-modem router does not work as a DNS server,
but if you have it setup as a DHCP server then it will provide name server IPs
to DHPC clients. What model of router is this?
> For some reason (I know
not what) Windows networking (including accessing the Internet) will not work if
I disable DHCP in the router and go completely manual with the IP
assignments.
Internet access is dependent on
IP and DNS. Windows networking (and I'm assuming you mean the Network
Neighborhood') is dependent on NetBEUI broadcasts, or WINS.
Your Internet problem is
probably that set the IP addresses to something acceptable but didn't set
the DNS settings right (192.168.1.1 is NOT right). Try this; with the
router and a Windows client set to DHCP, bring up a DOS command prompt on the
Windows box and issue the command 'ipconfig /all' and see what the DNS servers
are. You should find that it is NOT 192.168 anything, but rather it is
some IP out on the internet. If you manually set the IPs and DNS servers
to the addresses you find with the 'ipconfig' command then the system should
still work as before. Fixed IP addresses should not affect NetBEUI
broadcasts at all, i.e. your Network Neighborhood should still function as
before.
> If the router serves as DNS to Windows, why not Linux? The router does not
serve DNS, it serves the IP address of your ISP's DNS nameservers to DHCP
clients. In one of these messages you showed us your /etc/resolv.conf
file. Having one of those means that you are not using any nameserver
information from your DHCP server. Your resolv.conf should contain the IP
address of your ISP's nameserver, not the IP of the router.
DHCP is a convenience for lo-tech networks.
With only six machines on your network you really can't build a case for needing
DHCP if it's messing you up so get rid of it and fix your IP addresses.
Just make sure you have the correct network settings before you get
started. Your netmask, the gateway IP (the router) and your nameservers
IPs (at the ISP) will be the same for all your machines. Since you're
running Samba on the Linux box, you could share your hosts file to the Windows
machines. Just modify your hosts file there and just cut-n-paste
everything but the localhost entry into all your Window's boxes host
files. You only have to do this again if you add or remove a
machine.
If you want to run an Oracle server in a Windows
network, why not run it on a Windows machine. Then you won't have
'mixed-environment' problems. If your goal is just to have a
database server this may all be unnecessary. I don't think the Oracle server needs to be able ping your Windows boxes
by name to work, so really all you need to do is add the Linux box to the
Windows host files and be done with it. Greg
|
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
