On Ter, 22 Set 2009, Alexander Kaphuk wrote:
As far as my initial email being sent three times in a row. I do
apologise for the incident. I didn't do it on purpose though. I was
under the impression that I would receive a copy of that email
straight after sending it off. I thought that's wha
Sorry I took a while to reply to all those who had got back to me about
my query.
My network is up and running now. As it turned out, it was a simple
matter of getting my laptop ping the DSL modem before trying to connect
to the outside world. No manual configuration was required. I am fairly
Why on Earth need you send the same e-mail message three times in a row?
Do you think it'll get you attention? Quite the opposite. Please try to
send your dmesg and also look up dhclient.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
Hi,
I'm still having trouble configuring my wired network interface on
Debian Lenny running on HP Compaq Presario CQ61.
I put "auto eth0; iface eth0 inet dhcp" (each statment on separate line
as shown in debian wiki) into my /etc/network/interfaces file.
I ran "ifdown eth0; ifup eth0". I got
Hi,
I'm still having trouble configuring my wired network interface on
Debian Lenny running on HP Compaq Presario CQ61.
I put "auto eth0; iface eth0 inet dhcp" (each statment on separate line
as shown in debian wiki) into my /etc/network/interfaces file.
I ran "ifdown eth0; ifup eth0". I got
H.S. wrote:
Jabka Atu wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,..
I'm upgrading my small home network .
today i use /etc/hosts on each machine to figure out where each host
goe's as in :
192.168.0.1 whitebox.rent.net whitebox
192.168.0.2 bluebox.rent.net bluebox
192.168.0.3
Jabka Atu wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,..
I'm upgrading my small home network .
today i use /etc/hosts on each machine to figure out where each host
goe's as in :
192.168.0.1 whitebox.rent.net whitebox
192.168.0.2 bluebox.rent.net bluebox
192.168.0.3 blackbox.rent
On Thu, Mar 27, 2008 at 11:57:09PM -0400, Jabka Atu wrote:
> I'm upgrading my small home network .
> today i use /etc/hosts on each machine to figure out where each host
> goe's as in :
>
> 192.168.0.1 whitebox.rent.net whitebox
> 192.168.0.2 bluebox.rent.net bluebox
> 192.168.0.3 blackbox.rent.ne
On Thu, Mar 27, 2008 at 11:57:09PM -0400, Jabka Atu wrote:
> Hello,..
>
> I'm upgrading my small home network .
> today i use /etc/hosts on each machine to figure out where each host
> goe's as in :
>
> 192.168.0.1 whitebox.rent.net whitebox
> 192.168.0.2 bluebox.rent.net bluebox
> 192.168.0.3 bl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,..
I'm upgrading my small home network .
today i use /etc/hosts on each machine to figure out where each host
goe's as in :
192.168.0.1 whitebox.rent.net whitebox
192.168.0.2 bluebox.rent.net bluebox
192.168.0.3 blackbox.rent.net blackbox
sinc
Dear all,
I have a dhcp server on my net, which also provide hostnames based on
ip. Like if a machine get a ip of 192.168.1.147, then its hostname would be
ks147.
Now I have a debian box running on the net, and I have configured using
dhcp to get ip. But I do not know how to
First, good job on the D-I. I've put my Woody CD away for good now.
Second, and primarily: during setup, Sarge asked me for an IP address.
I just hit "enter" -- and it said my IP address was not entered
correctly. I suppose I could have gone to expert mode and done a DHCP
thing but how come
On Tue, Aug 19, 2003 at 10:16:29PM -0600, Jacob Anawalt wrote:
> likely comming from the server. You could ask them if the length of the
> lease you are getting is what they intended, and maybe provide some
> reasons for increasing the lease. I would be frustrated having the lease
> expire while
[EMAIL PROTECTED] wrote:
Hi,
I'm using DHCP to connect to the network, and I use ssh to contral
another machine. The problem is, my ip address is always changing. This
makes my ssh die. I wonder if it is because of my configure file is not
correct or is the common way of DHCP. By the way, I
> It sounds as though the lease times on the DHCP server are not long enough.
>
> A simple solution is to use a static IP address but this will depend on
> your ability to manually assign an IP address at the server end.
>
> HTH
>
> Clive
Well, one of my friends had the same problem, he wrote a
On Tue, Aug 19, 2003 at 11:49:27AM +0100, Clive Menzies wrote:
> It sounds as though the lease times on the DHCP server are not long enough.
>
> A simple solution is to use a static IP address but this will depend on
> your ability to manually assign an IP address at the server end.
>
> HTH
>
>
On (19/08/03 18:15), [EMAIL PROTECTED] wrote:
>
> I'm using DHCP to connect to the network, and I use ssh to contral
> another machine. The problem is, my ip address is always changing. This
> makes my ssh die. I wonder if it is because of my configure file is not
> correct
On Tue, 2003-08-19 at 20:15, [EMAIL PROTECTED] wrote:
> Hi,
>
> I'm using DHCP to connect to the network, and I use ssh to contral
> another machine. The problem is, my ip address is always changing. This
> makes my ssh die. I wonder if it is because of my configure file is
Hi,
I'm using DHCP to connect to the network, and I use ssh to contral
another machine. The problem is, my ip address is always changing. This
makes my ssh die. I wonder if it is because of my configure file is not
correct or is the common way of DHCP. By the way, I have never changed
the de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Apr 07, 2003 at 11:43:40AM +1000, Michael Wardle wrote:
> Add the following lines to /etc/dhcp3/dhcpd.conf:
> ddns-update-style interim;
> option domain-name-servers ;
>
> Add the folling lines to /etc/bind/named.conf:
> zone ".in-addr.arpa" I
On Sun, Apr 06, 2003 at 04:10:45PM +, Clive Menzies wrote:
> Hi Reaz
>
> I've got the nameservers in resolv.conf and so resolving public IP's is
> fine. It's the hosts on the local network that don't resolve. I tried
> including the DHCP server's IP address as a name server but that gave
On Sun, 6 Apr 2003 16:10:45 +
Clive Menzies <[EMAIL PROTECTED]> wrote:
> I've got the nameservers in resolv.conf and so resolving public IP's is
> fine. It's the hosts on the local network that don't resolve. I tried
> including the DHCP server's IP address as a name server but that gave
nameserver 24.153.22.195
Reaz
-Original Message-
From: Clive Menzies [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 05, 2003 8:39 PM
To: [EMAIL PROTECTED]
Subject: Resolving hostnames using DHCP
Hi
I've just installed Debian on an HP Netserver LH Pro which was a
challenge in itself
PROTECTED]
Sent: Saturday, April 05, 2003 8:39 PM
To: [EMAIL PROTECTED]
Subject: Resolving hostnames using DHCP
Hi
I've just installed Debian on an HP Netserver LH Pro which was a
challenge in itself ;). I am still very much a newbie and not very
technical. I've managed to get Linux
On Sunday, April 6, 2003, at 02:58 am, Mouammer H. Rayes wrote:
kata Clive Menzies
Hi
I've just installed Debian on an HP Netserver LH Pro which was a
challenge in itself ;). I am still very much a newbie and not very
technical. I've managed to get Linux running on an old Mac and a G4
plus w
Hi
I've just installed Debian on an HP Netserver LH Pro which was a
challenge in itself ;). I am still very much a newbie and not very
technical. I've managed to get Linux running on an old Mac and a G4
plus we've also got 3 Windows 98 PC's on the network. So far, I've
installed Samba and
Brendan O'Connor wrote:
>
> Looking further, I found out that my cable isp does not offer persistent
> hostnames. I checked what the hostname is under windows, and it's
> 'NAME.mn.rr.comDEST' which doesn't seem to mean anything (nor work with
> linux...) Any suggestions at all would be very
Looking further, I found out that my cable isp does not offer persistent
hostnames. I checked what the hostname is under windows, and it's
'NAME.mn.rr.comDEST' which doesn't seem to mean anything (nor work with
linux...) Any suggestions at all would be very helpful! Thanks!
--
On Mon, 23 Ap
Alright, thanks for the help!
--
On Mon, 23 Apr 2001 20:54:23
Mircea Luca wrote:
>Brendan O'Connor wrote:
>>
>> I have my ethernet card detected and working (using tulip.o, and etherconf
>> from Progeny), connected to a cable modem, but the internet isn't working at
>> all.
>>
>
>
>
>> # T
April 23, 2001 9:21 PM
To: debian-user@lists.debian.org
Cc: [EMAIL PROTECTED]
Subject: Using dhcp on a home cable connection
I have my ethernet card detected and working (using tulip.o, and etherconf
from Progeny), connected to a cable modem, but the internet isn't working at
all.
When I ru
Brendan O'Connor wrote:
>
> I have my ethernet card detected and working (using tulip.o, and etherconf
> from Progeny), connected to a cable modem, but the internet isn't working at
> all.
>
> # The ethernet interface, configured by etherconf
> iface eth0 inet dhcp
> hostname progeny
I have my ethernet card detected and working (using tulip.o, and etherconf from
Progeny), connected to a cable modem, but the internet isn't working at all.
When I run pump, I get a long pause, and "Operation failed." with no
further explanation. So I removed pump and installed dhcp-client.
Phil Brutsche writes:
> Samba won't necessarily work if you don't have the hostname pointing to
> the IP in /etc/hosts.
Are you saying that samba will may not work if you have both lines, like
this?
127.0.0.1 hasler.dhh hasler localhost
192.168.1.1 hasler.dhh h
On Fri, 31 Dec 1999, Salman Ahmed wrote:
ssahme >Could this be a case of the DHCP server treating Windows clients
ssahme >differently than non-Windows clients ? Majority of the DHCP clients at
ssahme >our place are Windoze boxes.
yes, if they are pointed at different DNS then anything is possible
A long time ago, in a galaxy far, far way, someone said...
> Salman Ahmed writes:
> > What should I add to this file so I can ping from the machine itself by
> > giving its fqdn hostname ?
>
> 127.0.0.1 matrix. matrix localhost.
>
> With this line any process on the machine can reach the machine
Salman Ahmed writes:
> But the second line in /etc/hosts will have to be updated/modified
> whenever the DHCP lease for that IP address runs out.
If you have a proper localhost line in /etc/hosts you don't actually need
the IP of your interface in there at all.
--
John Hasler
[EMAIL PROTECTED] (J
Salman Ahmed writes:
> What should I add to this file so I can ping from the machine itself by
> giving its fqdn hostname ?
127.0.0.1 matrix. matrix localhost.
With this line any process on the machine can reach the machine itself via
the fqdn, the hostname, or just 'localhost'.
Phil Brutsche wr
On Thu, 30 Dec 1999, Salman Ahmed wrote:
ssahme >
ssahme >Whenever I try to ping this machine (from itself) by giving the
ssahme >fqdn hostname, I get an error message like:
ssahme >
ssahme > unknown host matrix.domain.com
ssahme >
ssahme >nslookup on that fqdn hostname gives an error message sayi
<<< No Message Collected >>>
A long time ago, in a galaxy far, far way, someone said...
[...]
> Some more questions: I seem to be getting the same IP address through
> DHCP.
That's the way it works - each time you reboot you get the same IP until
the lease time runs out.
> After the DNS config update, I can ping this machin
On Thu, 30 Dec 1999, Salman Ahmed wrote:
ssahme >I got one of the network admins to update their DNS config so that the
ssahme >hostname of the machine is mapped to the machine's ethernet address.
ok
ssahme >Some more questions: I seem to be getting the same IP address through
ssahme >DHCP. Afte
On Wed, 29 Dec 1999, Salman Ahmed wrote:
ssahme >how this work ? Will this approach require the network sysadmins to
ssahme >change their (internal) DNS configuration ? Our network admins know of
ssahme >only one OS: Windoze, and generally don't know d*** about
ssahme >Unix/Linux/*BSD, so I am a l
you could add a domain to a DNS in your local network so that works, or
what is probably easier is look for the lmhosts file on the windows box
(use find) it may be called lmhosts.sam or some shit, add the ip and the
names there, it seems to be window's version of /etc/hosts. you may have
to renam
> My questions is can I use bind to solve my problmen?
>
> Is it posible to assign IP addresses to workstations using a look up table.
> So CP6 will always get's 192.168.1.6 as his IP address?
>
if machineA should always be 1.1.1.1 you add a line in the dhcp server's conf
binding the machine's M
Hai,
My workstations currently have static IP adresses, and I'm planning to
change this to a DHCP protocol.
I already have a DHCP daemon running on my unix box witch gives IP address
in the range
of 32..254 (CLASS C network). I use 1..32 for the current workstations
(staticly assigned).
On my uni
On Mon, 27 Oct 1997, Jason Washburn wrote:
> Has anyone has any luck connecting with DHCP, my campus uses is and I
> was
> wondering how I can hook up to the network that way...
Working without any problems here. package dhcpcd.
Brandon
-
Brandon Mitchell <[EMAIL PROTECTED]> "We a
Jason Washburn wrote:
> Has anyone has any luck connecting with DHCP, my campus uses is and I
> was
> wondering how I can hook up to the network that way...
Have you tried installing the dhcpcd package? It should get you up on the
network very easily.
--
see shy jo
--
TO UNSUBSCRIBE FRO
Has anyone has any luck connecting with DHCP, my campus uses is and I
was
wondering how I can hook up to the network that way...
Any help would be appreciated..
Jason
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [E
48 matches
Mail list logo
