OK. In the list below, the ones that involve FQDNs are all returning errors
tha indicate a DNS problem. If I am right in recalling that you can ping
the ISP's DNS server themselves by their addresses, I would suggest you see
if removing the on-LAN DNS server from the list in /etc/resolv.conf fix
# fx > Please tell us the *exact* command you entered and the *exact*
# fx > message ping
Sorry, truly.
These are exact results of ping via RHL :
ping 202.134.0.155 -c 1 :
PING 202.134.0.155(202.134.0.155) 56(84) bytes of data.
64 bytes from 202.134.0.155: icmp_seq=1 ttl=61 time=375 m
Comments embedded.
frans toruan wrote:
# fx > Hi, Frans:
# fx >
# fx > 10.234.16.101 fxrhl90 workstation's LAN interface
# fx > 10.234.16.99 ? gateway's LAN interface
# fx > 202.134.0.155 nsjkt1.telkom.net.id gateway's WAN interface
# fx > ?
# fx > 202.134.2.5 ns2.telkom.net.id a DNS s
At 11:09 AM 2/16/2005 +0700, frans toruan wrote:
[...]
# fx > Preliminary comment: When asking for technical help, never tell us
# fx > what the
# fx > response is "something like". Take the time to write it down and tell
# fx > us
# fx > what it actually is, and the exact command it is response to
Many thanks for your comments,
# fx >
# fx > Does your ISP have its own DNS servers? If so, you might need to use
# fx > dhcpcd (some
# fx > ISPs require you to use their own DNS servers to reduce network
# fx > load.)
Yes, 202.134.0.155 and 202.134.2.5 are DNS servers of our ISP. I already
inp
# fx > Hi, Frans:
# fx >
# fx > 10.234.16.101fxrhl90 workstation's LAN interface
# fx > 10.234.16.99 ? gateway's LAN interface
# fx > 202.134.0.155nsjkt1.telkom.net.idgateway's WAN interface
# fx > ?
# fx > 202.134.2.5 ns2.telkom.n
# fx > I don't quite understand this last sentence. The gateway number
# fx > should be
# fx > the LAN address of your router ... probably 10.234.16.99, based on
Yes, you are right.
# fx > what you
# fx > report below ... not (for example) the public address by which that
# fx > router
# fx > (pr
Comments interspersed.
At 03:14 PM 2/15/2005 +0700, GA Dept PT ACBI wrote:
I just installed RHL90, as workstation, and connected to our internal LAN.
Now, I tried to connect to the net via our ADSL. But failed, via Mozilla
browser, sendmail, or any other. The ADSL's IP number as default gateway was
GA Dept PT ACBI wrote:
I just installed RHL90, as workstation, and connected to our internal LAN.
Now, I tried to connect to the net via our ADSL. But failed, via Mozilla
browser, sendmail, or any other. The ADSL's IP number as default gateway was
already put into the routing table.
I can ping to
GA Dept PT ACBI wrote:
Data from /etc/sysconfig/networking/devices/ifcfg-eth0 :
DEVICE=eth0
BOOTPROTO=none
BROADCAST=10.234.16.255
IPADDR=10.234.16.101
NETMASK=255.255.255.0
NETWORK=10.234.16.0
ONBOOT=yes
HWADDR=00:0c:6e:6b:4e:c2
USERCTL=no
PEERDNS=no
GATEWAY=10.234.16.99
TYPE=Ethernet
Does your IS
10 matches
Mail list logo
