Larry,
Thanks for the tips. Very helpful.
The problem 1 solution was adding the router address as the gateway address
in the hosts, and setting a DNS address in the router and putting that in
the host machines. The fixed ip address machines now get on the internet.
For problem 2, the "iptables stop" moved me a notch closer on the NFS
setup. The Suse 9.1 machine mounted the file on the RH8 machine, but gave
this odd message (since it connects to the internet OK):
nfs server reported tcp not available, falling back to upd
Doing a "ls" on the mounted file doesn't show any folders (of which there
are a gazillion), but at least it's doing something and not just timing out.
Regards,
Don
At 07:20 AM 7/27/04, you wrote:
>On Mon, 2004-07-26 at 22:10, Donald E Haselwood wrote:
>
> > Problem 1:
> >
> > With DHCP enabled, I can ping the Suse 9.1<->WN98, and Suse 9.1<->RH8 by
> > address, but not by host name unless I manually go into the router, find
> > the assigned IP address, then plug them into the hosts files. This OK
> > except that at some time in the future I'll be doing something and the
> > addresses will be different (and by then I'll forgotten, and spend time
> > trying figure out what went wrong).
> >
> > If Suse 9.1 and RH8 are given fixed IPs, then I don't seem to get internet
> > access.
> > I tried putting access permission for the fixed IP in the router but
> > that didn't work.
> > Maybe this is a DNS issue, but if so, I haven't found the answer.
> > Somewhere I read the that WRT54G has a multicast problem--don't know
> > that is an issue here.
>
>Look at your router configuration. It should show what IP address span
>it is giving out in dhcp. ex 192.168.1.2 -> 192.168.1.31
>
>Use static IP addresses for the Linux boxen that are outside of that
>range. ex 192.168.1.100,192.168.1.101 etc.
>
>Set your gateway on those machines to your router's address.
>
>First try to set /etc/resolv.conf to show "nameserver 192.168.1.1"
>without the quotes where the ip address is the address of the router.
>Then "ping www.yahoo.com". If that doesn't work, change the ip after
>nameserver to the ip address your isp uses for name resolution. If that
>doesn't work try "ping 24.73.203.10". If that doesn't work, post
>another message to the list on this issue alone. This has to be working
>properly before moving to the next step.
>
>I have yet to find a cable modem type of router ie the one you are using
>that is set by default to block any ip addresses outside of that given
>out by dhcp. Although possible to do, I've never seen it set that way
>by default.
>
>If those tests are successful, then you need to do one of two things.
>You can either read up on dns to set up your own internal dns (not
>recommended for the size of your small network), or you can simply
>continue with your suggested solution of entries in the hosts files. I
>think hosts file resolution is perfect for your network.
>
>Now test to make sure you can ping each of your internal machines with
>"ping computername". If any of them fail, post back letting us know
>where it fails and only post about that issue. If they succeed you are
>done with problem 1. Problem two relies on this to be working smoothly.
>
> > I
> > Problem 2:
> >
> > Samba
> > I setup the Samba Client in Suse 9.1. When I do a browse Windows Network
> > (with the other machine running WN98) it pops up a "Unknown error
> condition
> > in stat: Network is unreachable" along with a msg to send in an error
> report...
> >
>
>Network is unreachable would fit if problem 1 wasn't solved. That being
>said, I have found it difficult to get network browsing working on
>various Distros. You may want to concentrate on getting the command
>line mounting of a folder working first.
>
> > NFS
> > I setup the RH8 /etc/export with a directory, /mnt/, and do
> > exportfs. exportfs shows the file has been exported with "<world>"
> > indicating that there shouldn't be a permissions problem.
> >
> > When I go to the Suse 9.1 and setup NFS Client, and do a Browse for NFS
> > servers, nothing shows up.
> > Doing it manually with, mount 10.1.1.100:/mnt /mnt, ends with a time
> > out. ping 10.1.1.100 works just fine.
> >
>
>On the machine that has the nfs share, make sure the nfs deamon is
>running. Then make sure there is no firewall set up. To make sure it
>is not... "/etc/init.d/iptables stop" should temporarily assure you that
>the default firewall setup is not blocking you. Test after stopping the
>firewall. You should be able to mount the folder being shared. If you
>still cannot connect to it you should post again and include the
>contents of your exports file and explain what you are getting.
>
>
>
> >
> > Any tips, suggestions, or soothing words would be appreciated.
> >
> >
>
>Your posting touched on several problems that rely on one another's
>successful setup in order to work. You should tackle the problems one
>at a time until solved before going on to the next for it to work. If
>problem 1 isn't solved, you'll never get problem 2 to work. (except for
>maybe the 10.1.1.100:/mnt /mnt which could have worked if certain
>conditions were met) Anyway, I wouldn't recommend working on 2 until 1
>is done.
>
>
>Sorry if I've "gone on" a bit. It is too early for this |-0
>
> > Regards,
> >
> > Don
> >
> >
> > -----------------------------------------------------------------------
> > This list is provided as an unmoderated internet service by Networked
> > Knowledge Systems (NKS). Views and opinions expressed in messages
> > posted are those of the author and do not necessarily reflect the
> > official policy or position of NKS or any of its employees.
> >
>
>-----------------------------------------------------------------------
>This list is provided as an unmoderated internet service by Networked
>Knowledge Systems (NKS). Views and opinions expressed in messages
>posted are those of the author and do not necessarily reflect the
>official policy or position of NKS or any of its employees.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 13:30:16 EDT