*Grasps at straws*
That all looks good to me. How about /etc/resolv.conf and /etc/hosts?
*Reaches into a hat*
It may just be that sometimes your card switches it's type of transmit
mode when the first few packets go out. My notebook card spams my
console/syslog with a few lines when it switches,
> The kernel should take care of the routing. What is your
> /etc/network/interfaces file look like? Just trying to probe to find a
> possible answer for you.
Here it is:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 171.64.93.186
network 171.64.93.0
The kernel should take care of the routing. What is your
/etc/network/interfaces file look like? Just trying to probe to find a
possible answer for you.
--mike
On 07 Aug 2001 10:12:12 -0700, Max Kamenetsky wrote:
> * Michael Heldebrant <[EMAIL PROTECTED]> [08/07/01 10:06] wrote:
> > Is this a dh
* Michael Heldebrant <[EMAIL PROTECTED]> [08/07/01 10:06] wrote:
> Is this a dhcp or static machine? I'm wondering if a default route is
> missing before the first mount and gets put in right afterwards. Sounds
> odd with the drivers compiled in. What card is it?
It's a static machine with a 3C
* Michael Heldebrant <[EMAIL PROTECTED]> [08/07/01 09:59] wrote:
> Are your network drivers compiled in or modules? If modules are they
> autoloaded in /etc/modules?
They're compiled in. I can see the network starting up way before the
portmapper and NFS mount requests are issued. Besides, the
Hi!
Whenever I reboot my system, I get the following error from
/etc/init.d/mountnfs.sh:
RPC: unable to receive, errno: no route to host
The result is that some NFS mount requests fail. The funny thing is
that this happens for only the first directory I try to mount from a
particular host.
6 matches
Mail list logo
