Re: PLESE help me with my kppp connection PLEASE

2001-09-22 Thread Martin Albert

On Saturday 22 September 2001 08:31, todd mansill wrote:
> My kppp connection fails giving the following message:
>
> The remote server is required to authenticate itself but I couldn't
--^^^--^
> find any suitanle secret(password) for it to use to do so.

You try to force your isp to authenticate against you. While this ... 
short, they're bigger, you loose.

The relevant config script (don't know what kppp produces, usually 
there are some of them hanging around) you have to define:

noauth

Please ask questions about using debian on the debian-user mailing list.

greetings, martin


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Strange delays - new to this Please Help! Thanks

2001-09-22 Thread Martin Albert

Hi, Todd!

You should first mail to debian-user for questions like this. d-anounce 
is definitely the wrong place. I left the other list adresses in for 
this mail, so that people know that there was an answer to your 
request. When you reply, please consider to remove some more.

I can only guess that you hosed your network setup.
Although networking is well structured, it may well look confusing to a 
newbie at first.

The reason for most delays are network packets send to unknown or 
unreachable hosts. Timeouts then are the only indication for the local 
host that sth. is wrong and they may take a while (you wouldn't want to 
loose your packets to mars because of timeouts).

The most important network inside your linux box is the unix network.

Everything else is for most installations TCP/IP networking.

Some files in the /etc directory (where all the configuration for your 
machine is stored) store the basic networking configuration:
hosts   - your local 'DNS'. Hostnames to IP-Numbers table. Only used when
host.conf - contains 'order host,...', see? The file
resolv.conf - at last stores adresses of name servers.

If any of your programs calls for a host by its name, this has to be 
translated (looked up) into the corresponding IP number, as the network 
itself doesn't know anything about names. If this lookup process is 
misconfigured, the resulting timeouts make up already for quite a delay.

Now all your packets have to find their way through the network. This 
is known as 'routing'. See the 'route' and 'ping' commands.

Most networking commands have an option like '-n', that makes them 
output (N)umbers instead of names. Trying one and the same command that 
hangs without -n once again with -n and it works, shows you clearly 
that you have a problem looking up names.

KDE is communicating a lot, fix your network and retry.

You found out that networking is very important these days.
Try to read up on how this is handled with linux and the tools.
You won't have to install obscure tools then, to try to make it, hm, 
work, as it did under this other non-free os ...

There are a lot of good readings on the internet. For a fine catalog 
with well defined topics you might want to look at 'dmoz.org'.
This one is FREE!

Have fun! martin


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Log top or similar information

2001-02-01 Thread Martin Albert

On Thu, 01 Feb 2001, David Lynn wrote:
> Hello -
> 
> Is there good method or a good application for logging top (or similar)
> information?  We'd like to capture all such information for historical
> performance monitoring, but top is not very capture-friendly.

Had a look at BSD accounting?
What data you need?

martin


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: multiple nics

2001-02-01 Thread Martin Albert

On Thu, 01 Feb 2001, James Mclean wrote:
> just curious to know how two network cards in servers work IE: in the
> ..
> 2 Intel EtherExpress Pro Fast Ethernet Cards ***
>
> would they be on separate IP addresses or the same one?  plugged into the same

Each network interface needs it's own (distinguishably ? what a word :)
IP address, so it knows which packets to take and for you to know what
address to send them to.

My /etc/networks/interfaces:

iface lo inet loopback

iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0

iface eth1 inet static
address 192.168.0.2
netmask 255.255.255.0

martin
 


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]