Hi,

Running v. 5.3, I have en0 configured for dhcp which works ok. However,
when I try to ping (or anything else) beyond the router, it can't be
reached. For some reason resolv.conf shows "domain example.org" and no
matter how I remove or change it (smitty, vi) it keeps showing up. BTW,
on v 5.1 (other machine) same thing happens. I once managed to fix that,
but very soon after it got back to the old situation and I haven't been
able to set it right again.
Help is appreciated.

Huub

On Jun 7, 1:34 pm, Huub <"v.niekerk at hccnet.nl"> wrote:
> Running v. 5.3, I have en0 configured for dhcp which works ok. However,
> when I try to ping (or anything else) beyond the router, it can't be
> reached. For some reason resolv.conf shows "domain example.org" and no

Hoi Huub,

This smells like a problem with the DHCP server. Example.org is just
the kind of domain you put in a default config file. I'm guessing that
your DHCP server doesn't supply the default router, name server and/or
domain. If the DHCP server runs AIX, check that all the appropriate
options are there:

network 172.16.1.0 255.255.255.0 {
option 1 255.255.255.0 # Netmask
option 3 172.16.1.1 # Default gateway
option 6 172.16.1.1 # Name server
option 4 172.16.1.1 # Time server
option 7 172.16.1.1 # Log server
option 15 utopia.com # Domain name

}

How you solve this if you're using an ADSL router, Linux or (FSM save
us) a Windows server depends on the platform.

Cheers,
Menno

>
> Hoi Huub,
>
> This smells like a problem with the DHCP server. Example.org is just
> the kind of domain you put in a default config file. I'm guessing that
> your DHCP server doesn't supply the default router, name server and/or
> domain. If the DHCP server runs AIX, check that all the appropriate
> options are there:
>

Hi Menno,

Thank you for your answer. The DHCP server indeed was the cause of the
domainname. However, though the domainname has been adjusted and
resolv.conf shows the correct info, I still have the problem. For a
short time I was able to ftp beyond the router on 4.3, but 5.3 still
didn't/doesn't go beyond the router. I compared resolv.conf, dhcpcd.ini,
defaultrouter and everything looks fine.
BTW, the DHCP server runs Debian Sparc.

On Jun 8, 8:20 am, Huub <"v.niekerk at hccnet.nl"> wrote:
> Hi Menno,
>
> Thank you for your answer. The DHCP server indeed was the cause of the
> domainname. However, though the domainname has been adjusted and
> resolv.conf shows the correct info, I still have the problem. For a
> short time I was able to ftp beyond the router on 4.3, but 5.3 still
> didn't/doesn't go beyond the router. I compared resolv.conf, dhcpcd.ini,
> defaultrouter and everything looks fine.
> BTW, the DHCP server runs Debian Sparc.

Well... That depends on whether you get the correct gateway from the
DHCP server. Check the obvious things like netstat -rn for the default
router and so on. Maybe the wrong default gateway is still in your
ODM. Check for "route" entries in lsattr -El inet0. If there is one,
remove it using smitty. I think the general idea is to get all these
numbers from DHCP, so you shouldn't have any configured in the ODM.


Cheers,
Menno