Re: [SLE] was Still troubled by NFS, now DNS!
On Mon, 2005-02-21 at 10:43, John wrote:
Ken Schneider wrote:
On Mon, 2005-02-21 at 09:58, John wrote:
Could you please post a copy of your /etc/hosts file and your /etc/resolv.conf file. There appears to be a problem with one or both of these files.
Also PLEASE only reply to the list! I don't need two copies of your reply.
Files attached. (replied off list because of ip addresses included)
J There was no need to reply off-list, the IP addresses are in the private IP address ranfe and cannot be routed in the internet.
______________________________________________________________________ nameserver 192.168.74.31 nameserver 192.168.74.23 nameserver 158.152.1.58 search dmj-consultancy.local
______________________________________________________________________
<snip>
# IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 10.0.0.31 General.DMJ-Consultancy.local 192.168.74.23 General.DMJ-Consultancy.local 192.168.74.31 General.DMJ-Consultancy.local General
You have two different addresses for the same server "general" that is probably causing the problem. When trying to attach to your server it is confused as to which address to use. Unless you are using a secondary address on your card -and- your network is setup to use two subnets you will have problems. Try removing, or commenting out the 10.0.0.31 and see what your results are. Also include the results of route -n so we can see what your routing table looks like. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Mon, 2005-02-21 at 10:43, John wrote:
Ken Schneider wrote:
On Mon, 2005-02-21 at 09:58, John wrote:
Could you please post a copy of your /etc/hosts file and your /etc/resolv.conf file. There appears to be a problem with one or both of these files.
Also PLEASE only reply to the list! I don't need two copies of your reply.
Files attached. (replied off list because of ip addresses included)
J
There was no need to reply off-list, the IP addresses are in the private IP address ranfe and cannot be routed in the internet.
______________________________________________________________________ nameserver 192.168.74.31 nameserver 192.168.74.23 nameserver 158.152.1.58 search dmj-consultancy.local
______________________________________________________________________
<snip>
# IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 10.0.0.31 General.DMJ-Consultancy.local 192.168.74.23 General.DMJ-Consultancy.local 192.168.74.31 General.DMJ-Consultancy.local General
You have two different addresses for the same server "general" that is probably causing the problem. When trying to attach to your server it is confused as to which address to use. Unless you are using a secondary address on your card -and- your network is setup to use two subnets you will have problems. Try removing, or commenting out the 10.0.0.31 and see what your results are. Also include the results of route -n so we can see what your routing table looks like.
There are three addresses for the one server: 10... = WAN, ...23 = WLAN and ...31 = LAN, all are separate cards. There is no connection outside the server between these networks. (not even a vpn yet!) Both the XP workstation and the laptop are currently working through the LAN card only. Pointing a browser at www.dmj-consultancy.org.uk and www.dmj-consultancy.me.uk should demonstrate that the WAN side is OK (observe the text in the main pane of the display - it should mimic the domain chosen). However, I've commented out the WLAN and WAN references in hosts and tried again. That appears to make no difference. I've attached the routing information you requested Thanks J Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.74.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.74.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 10.0.0.2 0.0.0.0 UG 0 0 0 eth0
On Mon, 2005-02-21 at 14:21, John wrote:
Ken Schneider wrote:
Could you please post a copy of your /etc/hosts file and your /etc/resolv.conf file. There appears to be a problem with one or both of these files.
Also PLEASE only reply to the list! I don't need two copies of your reply.
______________________________________________________________________ nameserver 192.168.74.31 nameserver 192.168.74.23
These are both the same machine so I don't understand them both being here.
nameserver 158.152.1.58 search dmj-consultancy.local
______________________________________________________________________
# IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 10.0.0.31 General.DMJ-Consultancy.local 192.168.74.23 General.DMJ-Consultancy.local 192.168.74.31 General.DMJ-Consultancy.local General
You have two different addresses for the same server "general" that is probably causing the problem. When trying to attach to your server it is confused as to which address to use. Unless you are using a secondary address on your card -and- your network is setup to use two subnets you will have problems. Try removing, or commenting out the 10.0.0.31 and see what your results are. Also include the results of route -n so we can see what your routing table looks like.
There are three addresses for the one server: 10... = WAN, ...23 = WLAN and ...31 = LAN, all are separate cards. There is no connection outside the server between these networks. (not even a vpn yet!)
Except ...23 and ...31 are -not- different networks. They are in the same subnet and may cause routing problems. I don't think you have NFS or DNS problems at all but have network issues you need to study and fix first. Draw up a diagram of your network and study it trying to visualize how packets get from point A to point B to point C and how having two network cards in the same subnet may cause routing issues. As I see it you don't need a separate card for the WLAN if it is in the same subnet as the LAN, that should be handled by the router.
Both the XP workstation and the laptop are currently working through the LAN card only. Pointing a browser at www.dmj-consultancy.org.uk and www.dmj-consultancy.me.uk should demonstrate that the WAN side is OK (observe the text in the main pane of the display - it should mimic the domain chosen).
However, I've commented out the WLAN and WAN references in hosts and tried again. That appears to make no difference.
I've attached the routing information you requested
Thanks
J
______________________________________________________________________ Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.74.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.74.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 10.0.0.2 0.0.0.0 UG 0 0 0 eth0
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Mon, 2005-02-21 at 14:21, John wrote:
Ken Schneider wrote:
Could you please post a copy of your /etc/hosts file and your /etc/resolv.conf file. There appears to be a problem with one or both of these files.
Also PLEASE only reply to the list! I don't need two copies of your reply.
______________________________________________________________________ nameserver 192.168.74.31 nameserver 192.168.74.23
These are both the same machine so I don't understand them both being here.
nameserver 158.152.1.58 search dmj-consultancy.local
______________________________________________________________________
# IP-Address Full-Qualified-Hostname Short-Hostname #
127.0.0.1 localhost
# special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 10.0.0.31 General.DMJ-Consultancy.local 192.168.74.23 General.DMJ-Consultancy.local 192.168.74.31 General.DMJ-Consultancy.local General
You have two different addresses for the same server "general" that is probably causing the problem. When trying to attach to your server it is confused as to which address to use. Unless you are using a secondary address on your card -and- your network is setup to use two subnets you will have problems. Try removing, or commenting out the 10.0.0.31 and see what your results are. Also include the results of route -n so we can see what your routing table looks like.
There are three addresses for the one server: 10... = WAN, ...23 = WLAN and ...31 = LAN, all are separate cards. There is no connection outside the server between these networks. (not even a vpn yet!)
Except ...23 and ...31 are -not- different networks. They are in the same subnet and may cause routing problems.
I don't think you have NFS or DNS problems at all but have network issues you need to study and fix first. Draw up a diagram of your network and study it trying to visualize how packets get from point A to point B to point C and how having two network cards in the same subnet may cause routing issues. As I see it you don't need a separate card for the WLAN if it is in the same subnet as the LAN, that should be handled by the router.
Both the XP workstation and the laptop are currently working through the LAN card only. Pointing a browser at www.dmj-consultancy.org.uk and www.dmj-consultancy.me.uk should demonstrate that the WAN side is OK (observe the text in the main pane of the display - it should mimic the domain chosen).
However, I've commented out the WLAN and WAN references in hosts and tried again. That appears to make no difference.
I've attached the routing information you requested
Thanks
J
______________________________________________________________________ Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.74.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.74.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 10.0.0.2 0.0.0.0 UG 0 0 0 eth0
...23 and ...31 have to be separate cards - WLAN is wireless, LAN is cable. Ordinarily, I'd have a bridge between them allowing my wireless network to communicate directly with my cable network. If you like, it's using the computer as a wireless access point instead of having a separate box.
Did you check the two web sites, both hosted by the WAN card? J
...23 and ...31 have to be separate cards - WLAN is wireless, LAN is cable. Ordinarily, I'd have a bridge between them allowing my wireless network to communicate directly with my cable network. If you like, it's using the computer as a wireless access point instead of having a separate box.
Did you check the two web sites, both hosted by the WAN card?
If you have separate cards then they should be on separate subnets. Assigning IPs on the same subnet to 2 different cards on the same box is just asking for trouble, and using the same alias for each interface is even worse. While I've heard it's possible to make this work with advanced routing, it won't work the way you have it configured. Once your routing is straightened out the NFS and DNS issues should be resolved. Jeff
Jeffrey Laramie wrote:
...23 and ...31 have to be separate cards - WLAN is wireless, LAN is cable. Ordinarily, I'd have a bridge between them allowing my wireless network to communicate directly with my cable network. If you like, it's using the computer as a wireless access point instead of having a separate box.
Did you check the two web sites, both hosted by the WAN card?
If you have separate cards then they should be on separate subnets. Assigning IPs on the same subnet to 2 different cards on the same box is just asking for trouble, and using the same alias for each interface is even worse. While I've heard it's possible to make this work with advanced routing, it won't work the way you have it configured. Once your routing is straightened out the NFS and DNS issues should be resolved.
Jeff
What's the difference between doing the bridging between wireless and cable this way over using an expensive access point in a separate box? That doesn't need separate subnets. J
participants (3)
-
Jeffrey Laramie -
John -
Ken Schneider