t; > pueda contactar?
> >
> > El mirror status actual es "ulises.hostalia.com ftp.es.debian.org:
> > [Errno 111] Connection refused"
> >
> > Un saludo.
> >
>
> Hola
>
> El equipo que se encarga de las réplicas tiene una lista de
o 111] Connection refused"
Un saludo.
Hola
El equipo que se encarga de las réplicas tiene una lista de correo en
debian-mirr...@lists.debian.org. Tienes más información en la página
wiki https://wiki.debian.org/Teams/Mirrors
Hola.
Parece que el servidor de réplicas está caído o tiene algún tipo de problema de
conectividad.
¿Hay algún mantenedor en la lista a quién se pueda contactar?
El mirror status actual es "ulises.hostalia.com ftp.es.debian.org: [Errno 111]
Connection refused"
Un saludo.
dif à faire dans la config de SSHD, mais je n'ai
> pas encore cherché pourquoi.
>
> cordialement
>
> Le 24/07/2019 à 13:21, G2PC a écrit :
>> SSH - channel xx: open failed: connect failed: Connection refused
>> #SSH <https://www.facebook.com/hashtag/ssh?source=note=HASHTA
3:21, G2PC a écrit :
SSH - channel xx: open failed: connect failed: Connection refused
#SSH <https://www.facebook.com/hashtag/ssh?source=note=HASHTAG>
#Tunnel
<https://www.facebook.com/hashtag/tunnel?source=note=HASHTAG>
#Question
<https://www.facebook.com/hashtag/question?source=
SSH - channel xx: open failed: connect failed: Connection refused
#SSH <https://www.facebook.com/hashtag/ssh?source=note=HASHTAG>
#Tunnel
<https://www.facebook.com/hashtag/tunnel?source=note=HASHTAG>
#Question
<https://www.facebook.com/hashtag/question?source=note=HASHTAG>
On Mon 19 Jun 2017 at 14:43:08 -0400, Felix Miata wrote:
> Greg Wooledge composed on 2017-06-19 11:05 (UTC-0400):
>
> > On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote:
> .
> >> I have a dozen machines with Stretch installed, most with Jessie and/or
> >> Sid as
> >> well. Only
Greg Wooledge composed on 2017-06-19 11:05 (UTC-0400):
> On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote:
.
>> I have a dozen machines with Stretch installed, most with Jessie and/or Sid
>> as
>> well. Only Stretch on host big41 produces the subject problem.
.
> According to a
On Mon, 19 Jun 2017, Brian wrote:
> The same experience as yours on tty1 to tty6. Except a couple of days
> ago when I used nouveau.modeset=0 on GRUB's linux line and got what is
> in the subject header.
Kernel modeset must be enabled non-root X to work, as you found out...
--
Henrique
On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote:
> I have a dozen machines with Stretch installed, most with Jessie and/or Sid as
> well. Only Stretch on host big41 produces the subject problem.
According to a previous message in this thread, it could be triggered
by a specific kernel
Greg Wooledge composed on 2017-06-19 09:29 (UTC-0400):
.
> On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote:
.
>> When I try as ordinary user (on host big41), I get the subject message.
>> Anyone
>> know how to get startx to work in Stretch, either on :0, :1 or :2, with or
>> without a
On Mon 19 Jun 2017 at 09:29:40 -0400, Greg Wooledge wrote:
> On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote:
> > When I try as ordinary user (on host big41), I get the subject message.
> > Anyone
> > know how to get startx to work in Stretch, either on :0, :1 or :2, with or
> >
On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote:
> When I try as ordinary user (on host big41), I get the subject message. Anyone
> know how to get startx to work in Stretch, either on :0, :1 or :2, with or
> without a greeter running (multi-user.targer vs. graphical.target)?
I've
>From the release notes:
2.2.10. The Xorg server no longer requires root
In the stretch version of Xorg, it is possible to run the Xorg
server as a regular user rather than as root. This reduces the
risk of privilege escalation via bugs in the X server. However,
it has some
Hi,
I was installed all packages which I need - blueman, bluemon,
blueproximity, bluetooth, bluewho, bluez... almost all which I found in
synaptic by bluetooth searchkey.
I wish to browse my phone but always I tried it gives me the Connection
refused error message.
Some days before this error
phone but always I tried it gives me the Connection
refused error message.
Some days before this error - after when I first install the packages I
mentioned it worked succesfully, but I don't know what happened now.
Please help solve this
Thanks
On Du, 06 mai 12, 22:23:56, Charles Kroeger wrote:
anyway, I couldn't get the X back up until I created that /etc/X11/xorg.conf
file again. (a very simple one) but after that, all was once again well.
If you want any help with this please attach the full
/var/log/Xorg.0.log when you try to
On Mon, 07 May 2012 20:50:01 +0200
Andrei POPESCU andreimpope...@gmail.com wrote:
On Du, 06 mai 12, 22:23:56, Charles Kroeger wrote:
anyway, I couldn't get the X back up until I created that /etc/X11/xorg.conf
file again. (a very simple one) but after that, all was once again well.
If
On Vi, 04 mai 12, 20:07:57, Charles Kroeger wrote:
After the dist-upgrade on sid during the 'transitions' I noticed there was
'no' /etc/X11/xorg.conf file at all so I created one
If you did fine without one before it should work now as well.
Kind regards,
Andrei
--
Offtopic discussions among
On Sun, 06 May 2012 11:30:02 +0200
Andrei POPESCU andreimpope...@gmail.com wrote:
If you did fine without one before it should work now as well.
It is curious to be sure. But when I tried to edit the /etc/X11/xorg.conf 'after
the dist-upgrade' when startx failed to start the nvidia driver,
After the dist-upgrade on sid during the 'transitions' I noticed there was
'no' /etc/X11/xorg.conf file at all so I created one
I also added the meta package:
xorg
also there was no xserver-xorg package after the dist-upgrade this was the
reason
I was seeing in my error message after startx:
Indulekha wrote:
Charles Kroeger wrote:
$startx
/etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found
Appears you no longer have the xserver installed.
Upgrade get interrupted, or finish with errors perhaps?
I noticed today that an 'apt-get dist-upgrade' in Sid wanted to remove
: connection refused
xinit: server error
I had a look at /etc/X11/xinit/xserverrc
#!/bin/sh
exec /usr/bin/X -no listen tcp $e
well this is mud to me, any suggestions as to what the message might mean?
I use the nvidia-glx video driver.
X on Sid seems to be going through a transition
Bob Proulx:
I noticed today that an 'apt-get dist-upgrade' in Sid wanted to remove
xserver-xorg and much of the rest of the X system.
That's why I habitually only run 'apt-get upgrade', as it will never
remove any packages and you can use it more or less blindly in order to
receive
Jochen Spieker m...@well-adjusted.de (02/05/2012):
Incidentally, apt-get dist-upgrade is less disastrous in this case. It
only suggests to remove xserver-xorg-video-all,
xserver-xorg-video-s3virge and xserver-xorg-video-tdfx while keeping
all important X related packages for my system.
After a dist-upgrade to an AMD64 wheezy/sid installation I get the following:
$startx
/etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found
xinit: giving up
xinit: unable to connect to X server: connection refused
xinit: server error
I had a look at /etc/X11/xinit/xserverrc
#!/bin/sh
exec
On Tue, May 01, 2012 at 06:13:51PM -0500, Charles Kroeger wrote:
After a dist-upgrade to an AMD64 wheezy/sid installation I get the following:
$startx
/etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found
xinit: giving up
xinit: unable to connect to X server: connection refused
xinit
On Wed, 02 May 2012 02:00:02 +0200
Indulekha indule...@theunworthy.com wrote:
Appears you no longer have the xserver installed.
Upgrade get interrupted, or finish with errors perhaps?
Thanks for your response however I'm not sure it isn't something else as all
the nividia-glx 295.40-1
On Tue, May 01, 2012 at 09:53:55PM -0500, Charles Kroeger wrote:
On Wed, 02 May 2012 02:00:02 +0200
Indulekha indule...@theunworthy.com wrote:
Appears you no longer have the xserver installed.
Upgrade get interrupted, or finish with errors perhaps?
Thanks for your response however
=node0sr0
device-config:device=/dev/mapper/vg_xcp-lv_xcp
Error: Connection refused (calling connect )
If I try to get help with xe, I get the same error:
# xe help
Error: Connection refused (calling connect )
Shouldn't that command be xe -help or xe --help? :-?
Any suggestions
On 04/29/2012 06:58 AM, Camaleón wrote:
Thanks for the reply. :-)
Shouldn't that command be xe -help or xe --help? :-?
That's what I thought on the first try. 'man xe' indicates help is a
command, not an option.
I've never used that package but I would ensure to carefully follow the
: Connection refused (calling connect )
If I try to get help with xe, I get the same error:
# xe help
Error: Connection refused (calling connect )
Any suggestions?
TIA,
David
p.s. Is there a better mailing list to get support for xcp-xapi?
--
To UNSUBSCRIBE, email to debian-user-requ
El Sat, 19 Nov 2011 16:50:30 -0300, Robert J. Briones C. escribió:
Estimados tengo el siguiente error.
cuando pongo /etc/init.d/bind9 reload sale el siguiente error.
Reloading domain name service...: bind9rndc: connect failed:
127.0.0.1#953: connection refused
failed!
(...)
Tienes un
Estimados tengo el siguiente error.
cuando pongo /etc/init.d/bind9 reload sale el siguiente error.
Reloading domain name service...: bind9rndc: connect failed:
127.0.0.1#953: connection refused
failed!
reviso el log
resultado del #tail -f /var/log/daemon.log
Nov 19 16:38:20 server named[27728
aptitude install postfix-tls libsasl2-modules sasl2-bin ?
Je les ai tous.
Ne pas oublier de redémarrer saslauthd ! Si effectivement le groupe
sasl n'était pas fait,
ni la modif chroot tu devrais lire le dernier paragraphe de mon site
(lien fournit sur ce fil)
Je ne sais plus pourquoi : le
Le 12.09.2011 19:01, JC a écrit :
Je me rappelle avoir eu des soucis aussi avec sasl (et mon ldap)
Un certain nombre de trucs que j'avais noté à l'époque :
- Attention Postfix est chrooté par défaut.
Il faut donc déplacer l'endroit ou se trouve le daemon saslauthd
sinon postfix ne le
Bonjour, Bonsoir,
Le Tue, 13 Sep 2011 08:11:01 +0200, Roland Vogt, vous avez écrit :
Le 12.09.2011 19:01, JC a écrit :
Je me rappelle avoir eu des soucis aussi avec sasl (et mon
ldap)
Un certain nombre de trucs que j'avais noté à l'époque :
- Attention Postfix est chrooté par
aptitude install postfix-tls libsasl2-modules sasl2-bin ?
Je les ai tous.
Ne pas oublier de redémarrer saslauthd ! Si effectivement le groupe
sasl n'était pas fait,
ni la modif chroot tu devrais lire le dernier paragraphe de mon site
(lien fournit sur ce fil)
Je ne sais plus pourquoi : le
venir puisque l'utilise PLAIN) je peux voir dans mon
mail.log un jolie Connection Refused.
Dans mon fichier /etc/default/saslauthd :
NAME=saslauthd
MECHANISMS=pam
MECH_OPTIONS=
THREADS=5
OPTIONS=-c -m /var/run/saslauthd -r
/etc/postfix/sasl/smtpd.conf :
pwcheck_method: saslauthd
saslauthd_path
Bonjour, Bonsoir,
Le Mon, 12 Sep 2011 14:59:29 +0200, Roland Vogt, vous avez écrit :
Est-ce que quelqu'un a un idée ? Parce que là... Je vois plus quoi
faire...
/etc/postfix/sasl/smtpd.conf
pwcheck_method: saslauthd
cram-md5 mech_list: plain login cram-md5 ...
/etc/postfix/main.cf
to saslauthd
server: Connection refused
warning: host.domain.local[192.168.170.85]: SASL LOGIN authentication
failed: generic failure
host.domain.local[192.168.170.85]: 535 5.7.8 Error: authentication
failed: generic failure
host.domain.local[192.168.170.85]: QUIT
Une autre idée ?
ça marche mieux
Bonjour, Bonsoir,
[je remets encore sur la liste]
Le Mon, 12 Sep 2011 15:50:45 +0200, Roland Vogt, vous avez écrit :
Une autre idée ?
ça marche mieux si je donne la bonne info, j'ai confondu
recipient_restrictions et client_restrictions :
/etc/postfix/main.cf
[...]
Je me rappelle avoir eu des soucis aussi avec sasl (et mon ldap)
Un certain nombre de trucs que j'avais noté à l'époque :
- Attention Postfix est chrooté par défaut.
Il faut donc déplacer l'endroit ou se trouve le daemon saslauthd
sinon postfix ne le voit pas.
Note: See
samedi 07 août 2010 à 01:05:31, Pascal Hambourg a écrit :
Salut,
m3t4linux a écrit :
La consultation de /var/log/mail.err comporte les messages suivants :
fetchmail[1709]: connection to localhost:smtp [::1/25] failed: Connection
refused
Cela me semble limpide : la connexion au
On Tue, Aug 10, 2010 at 10:01:31AM +0200, Eric KOM wrote:
Good morning!
Please, when I try to update my sources.list of one of my machine, I
receive this message error:
[skipped]
How is it now? I can log in to your mirror by FTP and in MOTD it says that
they
have limit of 500 users at
On Tue, Aug 10, 2010 at 10:01:31AM +0200, Eric KOM wrote:
Good morning!
Please, when I try to update my sources.list of one of my machine, I
receive this message error:
[skipped]
How is it now? I can log in to your mirror by FTP and in MOTD it says that they
have limit of 500 users at a
Good morning!
Please, when I try to update my sources.list of one of my machine, I
receive this message error:
nina:~# aptitude update
Err ftp://debian.mirror.ac.za sid Release.gpg
Could not connect to debian.mirror.ac.za:21 (192.168.0.4). - connect
(111: Connection refused)
Err ftp
Bonsoir à tous!!
La consultation de /var/log/mail.err comporte les messages suivants :
fetchmail[1709]: connection to localhost:smtp [::1/25] failed: Connection
refused
J'ai un compte gmail et voici ma config' email :
MTA/exim4 , MDA/procmail, MRA/fetchmail, MUA/mutt
J'envois et reçois
Salut,
m3t4linux a écrit :
La consultation de /var/log/mail.err comporte les messages suivants :
fetchmail[1709]: connection to localhost:smtp [::1/25] failed: Connection
refused
Cela me semble limpide : la connexion au port 25 de localhost en IPv6
(adresse ::1) a été refusée. Soit
--log-target=syslog
but if I try to connect with any of the tool such as pavucontrol for example I
get a message: connection refused.
Running the pulseaudio manager says at the bottom:
Linked to library version: 0.9.17
Compiled with library version: 0.9.8
don't know if this is any clue, or whether
:
RPC: Remote system error - Connection refused
Network connectivity okay:
* I can ping the server from the client.
* The client can also access the server's webserver.
* Iptables -L shows no filter rules on client nor server (all ACCEPT)
* Wireshark on the server shows that packets
There is something strange going on because I also tried httperf, and
it doesn't receive any response even when testing against 127.0.0.1
(to remove network problems if they are).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ab (apache bench) refuses to work, and I garnted with the following
error message:
--
apr_socket_recv: Connection refused (111)
--
My setup:
Debian Etch virtual machine running on Xen 3.2.1 with Debian-xen
kernel 2.6.18. ab was installed with aptitude install apache2-utils
I tried with both
.
Then, I can see that inetutils-inetd is running fine:
$ ps -eaf | grep [i]net
root 18129 1 0 10:48 ?00:00:00 /usr/sbin/inetutils-inetd
but still, when I use talk as me or root, I get:
Error on read from talk daemon: Connection refused
While trying to fix the problem myself, I
:
deskjet_6122?serial=MY2952B03P33: prnt/backend/hp.c 496: unable to
connect hpssd socket 2207: Connection refused
Après avoir fouillé le net un peu partout, je crois avoir tout fait...
# hp-check -t
HP Linux Imaging and Printing System (ver. 2.8.2)
Dependency/Version Check Utility ver. 13.0
Bonjour la liste,
J'ai un gros soucis depuis quelques jours, j'ai à ma disposition un serveur de
mail sous Debian externalisé (serveur dédié).
Des que je lance une connexion au serveur, j'ai en retour un connexion
refused, ssh,web, smtp, en telnet sur plusieurs ports.
J'ai bien sur désacttivé
West a écrit :
Bonjour la liste,
J'ai un gros soucis depuis quelques jours, j'ai à ma disposition un serveur de
mail sous Debian externalisé (serveur dédié).
Des que je lance une connexion au serveur, j'ai en retour un connexion
refused, ssh,web, smtp, en telnet sur plusieurs ports.
J'ai
Raphaël RIGNIER a écrit :
West a écrit :
Bonjour la liste,
J'ai un gros soucis depuis quelques jours, j'ai à ma disposition un
serveur de mail sous Debian externalisé (serveur dédié).
Des que je lance une connexion au serveur, j'ai en retour un
connexion refused, ssh,web, smtp, en telnet
Bonjour,
Le lundi 31 mars 2008, West a écrit...
Si quelqu'un peut me donner des id�es de recherche, car l� je vois
plus trop ou chercher, j'ai pass� la nuit la dessus sans resultat,
c'est peut etre un truc tout bete, mais je suis parti dans pas mal de
direction sans resultat, je
Bonjour,
Le lundi 31 mars 2008, West a écrit...
Si quelqu'un peut me donner des id�es de recherche, car l� je vois
plus trop ou chercher, j'ai pass� la nuit la dessus sans resultat,
c'est peut etre un truc tout bete, mais je suis parti dans pas mal de
direction sans resultat, je
On Sun, Oct 28, 2007 at 10:25:15PM -0500, Russell L. Harris wrote:
A day or two ago I began getting a 111 connection refused error when
attempting to access the debian repositories with Synaptic.
The command aptitude update also hangs.
However, Internet access with browser and mail
* Chris Bannister [EMAIL PROTECTED] [071030 20:00]:
On Sun, Oct 28, 2007 at 10:25:15PM -0500, Russell L. Harris wrote:
A day or two ago I began getting a 111 connection refused error when
attempting to access the debian repositories with Synaptic.
The command aptitude update also hangs
On Sun, Oct 28, 2007 at 22:25:15 -0500, Russell L. Harris wrote:
A day or two ago I began getting a 111 connection refused error when
attempting to access the debian repositories with Synaptic.
The command aptitude update also hangs.
However, Internet access with browser and mail appears
* Florian Kulzer [EMAIL PROTECTED] [071029 08:49]:
On Sun, Oct 28, 2007 at 22:25:15 -0500, Russell L. Harris wrote:
A day or two ago I began getting a 111 connection refused error when
attempting to access the debian repositories with Synaptic.
The command aptitude update also hangs
A day or two ago I began getting a 111 connection refused error when
attempting to access the debian repositories with Synaptic.
The command aptitude update also hangs.
However, Internet access with browser and mail appears to be normal.
Can someone recommend a diagnostic procedure?
RLH
Pessoal,
Estou tendo esse problema bom o meu Bind. Alguma sugestão?
[EMAIL PROTECTED]:~# /etc/init.d/bind9 restart* Stopping domain name service... rndc: connect failed: connection refused [ ok ]* Starting domain name service... [ ok ]
Obrigado,
Vinicius
Yahoo! Search
Música para ver e
também seria interessante.
[]'sOn 10/9/06, Vinicius Martins [EMAIL PROTECTED] wrote:
Pessoal,
Estou tendo esse problema bom o meu Bind. Alguma sugestão?
[EMAIL PROTECTED]:~# /etc/init.d/bind9 restart* Stopping domain name service... rndc: connect failed: connection refused [ ok ]* Starting domain
On 2006-07-05, Jim Seymour [EMAIL PROTECTED] wrote:
I added tcp_diag to the list of modules getting loaded at boot time.
That is the module it is looking for.
I added it with modprobe and that seems to have fixed the problem.
I'll add it to the boot configuration too.
Thanks,
Adam
--
To
On 2006-07-05, Jim Seymour [EMAIL PROTECTED] wrote:
identd[12299]: netlink_lookup: write failed: Connection refused
I added tcp_diag to the list of modules getting loaded at boot time.
That is the module it is looking for.
Thanks, I'll try that and see if goes away. Having googled a bit
Since I upgraded to a 2.6 kernel a few months ago, I've been getting
this message from logcheck (from syslog)
identd[12299]: netlink_lookup: write failed: Connection refused
at irregular intervals (sometimes several times in an hours, sometimes
not for a few days). I've googled
On Wed, 2006-07-05 at 15:21 +0100, Adam Funk wrote:
Since I upgraded to a 2.6 kernel a few months ago, I've been getting
this message from logcheck (from syslog)
identd[12299]: netlink_lookup: write failed: Connection refused
at irregular intervals (sometimes several times in an hours
Oi Luiz Motta,
Bom estou usando o Debian.
O postfix sim está rodando, e quando faço alguma alteração reinicio ele.
Uma outra coisa eh que o estou usando um servidor de DNS aqui da rede
que está instalado em outra máquina. Configurei o arquivo
resolv.conf e aparentemente está funcionando beleza.
Ich habe ein System auf Sid umgestellt, worauf mir nun nach einem Reboot
(Kernel Update) ohne Frage der SSH-Zugriff verwehrt wird. Von anderen Updates
kenne ich die Frage, ob eine Identifizierung nur per Key erlaubt sein soll.
Dafür gibt es sicher ein dpkg-reconfigure.
Gibt es eine Übersicht
On Mon, Sep 26, 2005 at 10:06:03PM +0200, Al Bogner wrote:
Ich habe ein System auf Sid umgestellt, worauf mir nun nach einem Reboot
(Kernel Update) ohne Frage der SSH-Zugriff verwehrt wird. Von anderen Updates
kenne ich die Frage, ob eine Identifizierung nur per Key erlaubt sein soll.
Dafür
On Mon, Sep 26, 2005 at 10:06:03PM +0200, Al Bogner wrote:
Gibt es eine Übersicht aller dpkg-reconfigure?
configure-debian.
Peter
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
Am Montag, den 26.09.2005, 22:06 +0200 schrieb Al Bogner:
Ich habe ein System auf Sid umgestellt, worauf mir nun nach einem Reboot
(Kernel Update) ohne Frage der SSH-Zugriff verwehrt wird.
Läuft der SSh-Server überhaupt? Könnte sonst auch an einem fehlenden
Gerät in /dev liegen.
Von anderen
Am Montag, 26. September 2005 22:12 schrieb Christoph Haas:
On Mon, Sep 26, 2005 at 10:06:03PM +0200, Al Bogner wrote:
Ich habe ein System auf Sid umgestellt, worauf mir nun nach einem Reboot
(Kernel Update) ohne Frage der SSH-Zugriff verwehrt wird. Von anderen
Updates kenne ich die Frage,
Am Montag, den 26.09.2005, 22:35 +0200 schrieb Al Bogner:
Am Montag, 26. September 2005 22:12 schrieb Christoph Haas:
On Mon, Sep 26, 2005 at 10:06:03PM +0200, Al Bogner wrote:
Ich habe ein System auf Sid umgestellt, worauf mir nun nach einem Reboot
(Kernel Update) ohne Frage der
[Ingrid on]
Am Montag, den 26.09.2005, 22:48 +0200 schrieb Daniel Leidert:
Am Montag, den 26.09.2005, 22:35 +0200 schrieb Al Bogner:
Am Montag, 26. September 2005 22:12 schrieb Christoph Haas:
On Mon, Sep 26, 2005 at 10:06:03PM +0200, Al Bogner wrote:
Ich habe ein System auf Sid
Am Montag, 26. September 2005 22:32 schrieb Daniel Leidert:
Von anderen Updates
kenne ich die Frage, ob eine Identifizierung nur per Key erlaubt sein
soll.
Sicher? Mir wurde diese Frage nie gestellt - weder unter Sarge, noch
unter Sid.
Habe ich gerade wieder bei der ssh-Installation
On Mon, Sep 26, 2005 at 11:16:17PM +0200, Al Bogner wrote:
Am Montag, 26. September 2005 22:32 schrieb Daniel Leidert:
Von anderen Updates
kenne ich die Frage, ob eine Identifizierung nur per Key erlaubt sein
soll.
Sicher? Mir wurde diese Frage nie gestellt - weder unter Sarge,
Am Montag, den 26.09.2005, 23:16 +0200 schrieb Al Bogner:
Am Montag, 26. September 2005 22:32 schrieb Daniel Leidert:
Von anderen Updates
kenne ich die Frage, ob eine Identifizierung nur per Key erlaubt sein
soll.
Sicher? Mir wurde diese Frage nie gestellt - weder unter Sarge, noch
, log_file = none,
log_lvl = 0
2005-09-01 10:57:37 [4986] [0] INFO: Host localhost Port 1 interval 0.100
max-messages 100
2005-09-01 10:57:37 [4986] [0] INFO: fakesmsc starting
2005-09-01 10:57:37 [4986] [0] ERROR: connect failed
2005-09-01 10:57:37 [4986] [0] ERROR: System error 111: Connection
Hi!!!
I had some problem and i resolve this problem specifying waht interface who i want to listen!
I hope you understands my english becose i'm from Brazil...
Bye,
Thiago Mourão
JEMF wrote:
Pessoal,
Fiz aqui um apt-get install ntp-simple. Ele coloca o ntp-server no ar e
a porta 123 também. A máquina é virgem. Não tem iptables ou tcp
wrappers. Quando tento conectar (ntpdate 127.0.0.1) dá connection refused.
O ntp-server só vai aceitar sincronizar outros qdo ele próprio
Marcos, tá muito estranho. Como estou fazendo experiências, já formatei
a máquina e já instalei novamente. O cliente diz que não havia servidor
para sincronizar. Mas a porta está lá. netstate -na mostra a porta 123
udp. Já se passaram 4 horas e nada... Estranho que o nmap mostra todos
os udp
Hallo,
amavis-postfix verweigert die Verbindung bei:
telnet localhost 10024
netstat -ln gibt aber folgende Ausgabe:
...
tcp 0 0 *:10024 *:* LISTEN
...
Auf port 25 und 10025 antwortet erwartungsgemäß postfix.
Die amavisd.conf habe ich auf den
Pos a lo dicho no se exactamente desde que actualizacion (es un equipo con
actualizacion casi diaria) pero no consigo montar los directorios que exporto
via nfs:
mount 192.168.1.2:/home/ftp/ /mnt/ftp
mount: RPC: Remote system error - Connection refused
Y que yo sepa no he tocado nada de la
/ftp
mount: RPC: Remote system error - Connection refused
Y que yo sepa no he tocado nada de la configuracion (que es muy simple para
compartir unos directorio dentro de la LAN).
Alguien ha tenido un problema semejante ?
A ver, ahora el portmap en configuración por defecto sólo escucha en
desde hace un par o tres días en SID.
mount 192.168.1.2:/home/ftp/ /mnt/ftp
mount: RPC: Remote system error - Connection refused
Y que yo sepa no he tocado nada de la configuracion (que es muy simple para
compartir unos directorio dentro de la LAN).
Alguien ha tenido un problema
- Connection refused
Y que yo sepa no he tocado nada de la configuracion (que es muy simple para
compartir unos directorio dentro de la LAN).
Alguien ha tenido un problema semejante ?
--
¿Tienes bien el /etc/hosts.allow?
Siempre que he tenido problemas es porque no estaban las
:
mount 192.168.1.2:/home/ftp/ /mnt/ftp
mount: RPC: Remote system error - Connection refused
Algunas veces me pasó algo similar, has tratado de limpiar tus tablas de
iptable en ambas máquinas ;) tal vez ayude un poco
#iptables -L #Tal vez este bloqueando ese tipo de tráfico
#iptables -F
Hi,
Both ethereal and tcpdump are giving me this error, and I'm not
finding much on google about it.
sbdcid222:~# tcpdump
tcpdump: getifaddrs: Connection refused
I also get this error upon starting Ethereal.
Anyone know what the problem might be?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
Seem to have got SAMBA working now, but don't seem to
be able to get the SWAT utility to work. Every time i
try to browse to http://localhost:901 I get connect
refused error.
Had a look at the samba.org site how tos, nothing
leaped out as obvious.
Any thoughts?
Stuart Murray wrote:
Seem to have got SAMBA working now, but don't seem to
be able to get the SWAT utility to work. Every time i
try to browse to http://localhost:901 I get connect
refused error.
Had a look at the samba.org site how tos, nothing
leaped out as obvious.
Any thoughts?
I'd suggest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stuart!
| try to browse to http://localhost:901 I get connect
| refused error.
Did you install SWAT (it's a seperate package in Debian) and did you
have a look into /etc/services? If I remeber right, you have to remove
the #off# at the beginning of
port 2025: Connection refused
Alors voilà j'aurais aimé savoir si ma configue marche sur internet car si
c'est le cas
c'est mon routeur que je dois configuré.
ou si sa ne marche pas et qu'elles sont les champs à changé ou à rajouter...
Merci
Mon routeur est un Sagem [EMAIL PROTECTED
-
et voici le problème:
ssh [EMAIL PROTECTED] -p 2025 #sa marche
ssh [EMAIL PROTECTED] -p 2025 # XXX ip du routeur
ssh: connect to host 83.165.87.111 port 2025: Connection refused
Alors voilà j'aurais aimé savoir si ma configue marche sur internet car si
c'est le cas
c'est mon routeur que
Subsystem sftp/usr/lib/sftp-server
UsePAM yes
-
et voici le problème:
ssh [EMAIL PROTECTED] -p 2025 #sa marche
ssh [EMAIL PROTECTED] -p 2025 # XXX ip du routeur
ssh: connect to host 83.165.87.111 port 2025: Connection refused
Alors voilà j'aurais aimé
: Connection refused
Alors voilà j'aurais aimé savoir si ma configue marche sur internet car si
c'est le cas
c'est mon routeur que je dois configuré.
ou si sa ne marche pas et qu'elles sont les champs à changé ou à rajouter...
Merci
Ca marche en localhost, donc le server est bien
1 - 100 of 263 matches
Mail list logo
