Re: [SLE] Internet Problem Over LAN
On Thursday 14 July 2005 06:03 pm, John Scott wrote:
On 7/14/05, John Andersen <jsa@pen.homeip.net> wrote:
On Thursday 14 July 2005 12:54 pm, James Wright wrote:
Apparently I have a DNS problem, but I can't seem to figure it out. For my DNS I had two local addresses (for the Windows Server 2003 boxes). I added one of the ISPs DNS to the list, but it did not resolve the problem.
You may be confused as to how the dns servers work. The second and third etc. dns servers are only used if the first one fails, (goes off line).
You need to open up a shell and ping the sites where these "unreachable pages" are. Ping by name, (not IP) and see if an ip is returned. If an ip Is returned, its not a dns problem.
Ping doesn't always provide as much info as it used to because some sites drop icmp echo_* packets from entering/leaving the network/host, I do (based on where it comes from). If he tries to ping (it won't hurt) and gets no response, it still may not mean anything.
But, as I instructed, it doesn't matter if the ping returns at all. All that the ping is for is to see if it will resolve a numeric IP when he pings a name. If so, regardless of whether the ping returns, its not a dns problem. The OP is jumping to the conclusion that he has a DNS problem when in fact some sites do work, which indicates that DNS is unlikely to be the real problem. -- _____________________________________ John Andersen
John Andersen wrote:
On Thursday 14 July 2005 06:03 pm, John Scott wrote:
On 7/14/05, John Andersen <jsa@pen.homeip.net> wrote:
On Thursday 14 July 2005 12:54 pm, James Wright wrote:
Apparently I have a DNS problem, but I can't seem to figure it out. For my DNS I had two local addresses (for the Windows Server 2003 boxes). I added one of the ISPs DNS to the list, but it did not resolve the problem.
You may be confused as to how the dns servers work. The second and third etc. dns servers are only used if the first one fails, (goes off line).
You need to open up a shell and ping the sites where these "unreachable pages" are. Ping by name, (not IP) and see if an ip is returned. If an ip Is returned, its not a dns problem
Excuse my previous reply. Ping does resolve the IP address, but the host is unreachable. nslookup can also resolve the IP address. I tried entering the ip address in the web browser, but it still did not load. Any suggestions? My /etc/resolve.conf shows:
search blackriverproduce.com nameserver 192.168.1.7 nameserver 192.168.1.4 blackriverproduce.com is the domain here. My host name is linux if that makes any difference. I have automatic address setup (via DHCP). I have change host name (via DHCP). Domain Search 1 is filled in as blackriverproduce.com. I have update name servers and search list via DHCP. Under routing I have my gateway set at 192.168.1.1. Enable IP forwarding is off. As I said before, I have tried changing the DNS to those provided by the ISP, but it does not change anything. I can change things on the Windows 2003 Server, but because Windows clients work, I do not really want to change any settings. If any additional info is needed I will be happy to post it. James W
On Friday 15 July 2005 09:50 am, James Wright wrote:
search blackriverproduce.com nameserver 192.168.1.7 nameserver 192.168.1.4
blackriverproduce.com is the domain here. My host name is linux if that makes any difference. I have automatic address setup (via DHCP). I have change host name (via DHCP). Domain Search 1 is filled in as blackriverproduce.com. I have update name servers and search list via DHCP. Under routing I have my gateway set at 192.168.1.1. Enable IP forwarding is off. As I said before, I have tried changing the DNS to those provided by the ISP, but it does not change anything. I can change things on the Windows 2003 Server, but because Windows clients work, I do not really want to change any settings. If any additional info is needed I will be happy to post it.
James W
Ok, then we have established that you don't have a DNS problem. The site names resolve to a numeric IP just fine. DNS is working. When you do a traceroute to the domain name or the IP, what does it show? Also, what site are you trying to reach that is unreachable? Is this site perchance hosted on your own network? (If so, this is an out-and-in-again problem which is problematic with some routers). -- _____________________________________ John Andersen
On Friday, July 15, 2005 @ 9:50 AM, James Wright wrote:
John Andersen wrote:
On Thursday 14 July 2005 06:03 pm, John Scott wrote:
On 7/14/05, John Andersen <jsa@pen.homeip.net> wrote:
On Thursday 14 July 2005 12:54 pm, James Wright wrote:
Apparently I have a DNS problem, but I can't seem to figure it out. For my DNS I had two local addresses (for the Windows Server 2003 boxes). I added one of the ISPs DNS to the list, but it did not resolve the problem.
You may be confused as to how the dns servers work. The second and third etc. dns servers are only used if the first one fails, (goes off line).
You need to open up a shell and ping the sites where these "unreachable pages" are. Ping by name, (not IP) and see if an ip is returned. If an ip Is returned, its not a dns problem
Excuse my previous reply. Ping does resolve the IP address, but the host is unreachable. nslookup can also resolve the IP address. I tried entering the ip address in the web browser, but it still did not load. Any suggestions? My /etc/resolve.conf shows:
search blackriverproduce.com nameserver 192.168.1.7 nameserver 192.168.1.4
blackriverproduce.com is the domain here. My host name is linux if that makes any difference. I have automatic address setup (via DHCP). I have change host name (via DHCP). Domain Search 1 is filled in as blackriverproduce.com. I have update name servers and search list via DHCP. Under routing I have my gateway set at 192.168.1.1. Enable IP forwarding is off. As I said before, I have tried changing the DNS to those provided by the ISP, but it does not change anything. I can change things on the Windows 2003 Server, but because Windows clients work, I do not really want to change any settings. If any additional info is needed I will be happy to post it.
James W
Shouldn't "Enable IP forwarding" be set on? Do you have a router at 192.168.1.1? Greg Wallace
On Friday 15 July 2005 11:21 pm, Greg Wallace wrote:
Shouldn't "Enable IP forwarding" be set on? Do you have a router at 192.168.1.1?
Greg Wallace
No, that is what you do when you want Linux to act as a router. Not needed when used as a stand alone machine or a machine on a network. -- _____________________________________ John Andersen
On Friday, July 15, 2005 @ 11:24 PM, John Anderson wrote:
On Friday 15 July 2005 11:21 pm, Greg Wallace wrote:
Shouldn't "Enable IP forwarding" be set on? Do you have a router at 192.168.1.1?
Greg Wallace
No, that is what you do when you want Linux to act as a router. Not needed when used as a stand alone machine or a machine on a network.
-- _____________________________________ John Andersen
Should he try adding the following entry to resolv.conf? -- nameserver 192.168.1.1 Greg W.
On Saturday 16 July 2005 12:28 am, Greg Wallace wrote:
On Friday, July 15, 2005 @ 11:24 PM, John Anderson wrote:
On Friday 15 July 2005 11:21 pm, Greg Wallace wrote:
Shouldn't "Enable IP forwarding" be set on? Do you have a router at 192.168.1.1?
Greg Wallace
No, that is what you do when you want Linux to act as a router. Not needed when used as a stand alone machine or a machine on a network.
-- _____________________________________ John Andersen
Should he try adding the following entry to resolv.conf? --
nameserver 192.168.1.1
Greg W.
Perhaps if resolv.conf has not already been set that way by the dhcpcd. However, as indicated in prior messages in this thread, his DNS IS WORKING. There is no problem with DNS. He can ping any of the problem sites by name and the IP is reported by the ping command (even though the ping is not successful). DNS lookups work fine. This is a routing problem, not a DNS problem. -- _____________________________________ John Andersen
On Saturday, July 15, 2005 @ 12:35 AM John Andersen wrote:
On Saturday 16 July 2005 12:28 am, Greg Wallace wrote:
On Friday, July 15, 2005 @ 11:24 PM, John Anderson wrote:
On Friday 15 July 2005 11:21 pm, Greg Wallace wrote:
Shouldn't "Enable IP forwarding" be set on? Do you have a router at 192.168.1.1?
Greg Wallace
No, that is what you do when you want Linux to act as a router. Not needed when used as a stand alone machine or a machine on a network.
-- _____________________________________ John Andersen
Should he try adding the following entry to resolv.conf? --
nameserver 192.168.1.1
Greg W.
Perhaps if resolv.conf has not already been set that way by the dhcpcd. However, as indicated in prior messages in this thread, his DNS IS WORKING.
There is no problem with DNS.
He can ping any of the problem sites by name and the IP is reported by the ping command (even though the ping is not successful). DNS lookups work fine.
This is a routing problem, not a DNS problem.
-- _____________________________________ John Andersen
Is there anything additional that he would need to set up on his SuSE machine to be able to communicate with a Windows name server? Greg Wallace
On Sat, 2005-07-16 at 01:25 -0800, Greg Wallace wrote:
On Saturday, July 15, 2005 @ 12:35 AM John Andersen wrote:
On Saturday 16 July 2005 12:28 am, Greg Wallace wrote: Perhaps if resolv.conf has not already been set that way by the dhcpcd. However, as indicated in prior messages in this thread, his DNS IS WORKING.
There is no problem with DNS.
He can ping any of the problem sites by name and the IP is reported by the ping command (even though the ping is not successful). DNS lookups work fine.
This is a routing problem, not a DNS problem.
As has been stated here a couple of times, he has no problems with DNS/name servers. It most likely is a routing issue. By the way, trying to ping outside hosts will not always work as a lot of outside hosts no longer respond to ping requests. The OP needs to find out the IP address of the inside router and set his default route to that address. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Saturday 16 July 2005 02:58 am, Ken Schneider wrote:
By the way, trying to ping outside hosts will not always work as a lot of outside hosts no longer respond to ping requests
Exactly. But the fact that he can resolve the IP of the outside host when pinging it by name emphasizes your first point, that its not a DNS/nameserver problem. Whether or not the ping actually works is immaterial. -- _____________________________________ John Andersen
It is not so important getting a response back but he resolution of the ip address that comes from the ping message. Ken Schneider wrote:
On Sat, 2005-07-16 at 01:25 -0800, Greg Wallace wrote:
On Saturday, July 15, 2005 @ 12:35 AM John Andersen wrote:
On Saturday 16 July 2005 12:28 am, Greg Wallace wrote: Perhaps if resolv.conf has not already been set that way by the dhcpcd. However, as indicated in prior messages in this thread, his DNS IS WORKING.
There is no problem with DNS.
He can ping any of the problem sites by name and the IP is reported by the ping command (even though the ping is not successful). DNS lookups work fine.
This is a routing problem, not a DNS problem.
As has been stated here a couple of times, he has no problems with DNS/name servers. It most likely is a routing issue. By the way, trying to ping outside hosts will not always work as a lot of outside hosts no longer respond to ping requests. The OP needs to find out the IP address of the inside router and set his default route to that address.
-- Joseph Loo jloo@acm.org
As has been stated here a couple of times, he has no problems with DNS/name servers. It most likely is a routing issue. By the way, trying to ping outside hosts will not always work as a lot of outside hosts no longer respond to ping requests. The OP needs to find out the IP address of the inside router and set his default route to that address.
We are using a SonicWall firewall as the router at address 192.168.1.1. All the Windows PCs use this as the default gateway. James W
On Sat, 2005-07-16 at 00:34 -0800, John Andersen wrote:
He can ping any of the problem sites by name and the IP is reported by the ping command (even though the ping is not successful). DNS lookups work fine.
This is a routing problem, not a DNS problem.
Can't we know this easily if he shows us the output of "/sbin/route" at the SuSE machines? Toshi
Can't we know this easily if he shows us the output of "/sbin/route" at the SuSE machines?
Toshi
/sbin/route shows this: black-kdavzbpz3:/home/james # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.102.0 * 255.255.255.0 U 0 0 0 vmnet8 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
On Tue, 2005-07-19 at 12:29 -0400, James Wright wrote:
/sbin/route shows this:
black-kdavzbpz3:/home/james # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.16.102.0 * 255.255.255.0 U 0 0 0 vmnet8 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
Sorry, I also want to see the output of /sbin/ifconfig as well. The result of your traceroute doesn't make sense to me. Toshi
participants (6)
-
Greg Wallace -
James Wright -
John Andersen -
Joseph Loo -
Ken Schneider -
Toshi Esumi