# Client XP sur DEBIAN server

**URL:** <https://www.debian-fr.org/t/client-xp-sur-debian-server/17471>\
**Category:** Support Debian\
**Created:** [Février 20, 2016, 6:49 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471 "2016-02-20T18:49:27Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/41 "2016-02-20T18:51:16Z")

</div>

bon alors là, c’est carrément la merde. Au point où on en était resté, lorsque j’ai restarté samba, j’ai eu le voyant alarm de mon router et plus du tout de communication sur le net. J’ai du retrouver mon pwd et le fichier de la config de mon router archivé en 2007. Et heureusement ça a marché sinon, je ne serai pas en train de t’écrire.  
Je te joint mon fichier smb.conf que j’ai surement déjà trop bricolé, ne t’étonne pas, j’ai mis les lignes qu’on a ajoutées en commentaires mais ça ne changeait rien au fait que mon routeur faisait le mort. je pense que tu arriveras à m’en faire un fichier qui tienne la route, Quand au réseau, effectivement il y avait un certain accès depuis xp.  
Je ne peux pas te joindre le fichier alors je colle le contenu:

# 

# Sample configuration file for the Samba suite for Debian GNU/Linux.

# 

# 

# This is the main Samba configuration file. You should read the

# smb.conf(5) manual page in order to understand the options listed

# here. Samba has a huge number of configurable options most of which

# are not shown in this example

# 

# Any line which starts with a ; (semi-colon) or a # (hash)

# is a comment and is ignored. In this example we will use a

# for commentary and a ; for parts of the config file that you

# may wish to enable

# 

# NOTE: Whenever you modify this file you should run the command

# “testparm” to check that you have not made any basic syntactic

# errors.

# 

#======================= Global Settings =======================

[global]

## Browsing/Identification

# Change this to the workgroup/NT-domain name your Samba server will part of

workgroup = MYGROUP

# netbios name=samba

# server string is the equivalent of the NT Description field

server string = %h server

# Windows Internet Name Serving Support Section:

# WINS Support - Tells the NMBD component of Samba to enable its WINS Server

; wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client

# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both

; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.

dns proxy = no

# What naming service and in what order should we use to resolve host names

# to IP addresses

; name resolve order = lmhosts host wins bcast

#### Networking

# The specific set of interfaces / networks to bind to

# This can be either the interface name or an IP address/netmask;

# interface names are normally preferred

; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the

# ‘interfaces’ option above to use this.

# It is recommended that you enable this feature if your Samba machine is

# not protected by a firewall or is a firewall itself. However, this

# option cannot handle dynamic or non-broadcast interfaces correctly.

; bind interfaces only = true

#### Debugging/Accounting

# This tells Samba to use a separate log file for each machine

# that connects

log file = /var/log/samba/log.%m

# Put a capping on the size of the log files (in Kb).

max log size = 1000

# If you want Samba to only log through syslog then set the following

# parameter to ‘yes’.

; syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything

# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log

# through syslog you should set the following parameter to something higher.

syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace

panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# “security = user” is always a good idea. This will require a Unix account

# in this server for every user accessing the server. See

# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html

# in the samba-doc package for details.

; security = user

# You may wish to use password encryption. See the section on

# ‘encrypt passwords’ in the smb.conf(5) manpage before enabling.

encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what

# password database type you are using.

passdb backend = tdbsam

obey pam restrictions = yes

; guest account = nobody  
invalid users = root

# This boolean parameter controls whether Samba attempts to sync the Unix

# password with the SMB password when the encrypted SMB password in the

# passdb is changed.

; unix password sync = no

# For Unix password sync to work on a Debian GNU/Linux system, the following

# parameters must be set (thanks to Ian Kahan \<[kahan@informatik.tu-muenchen.de](mailto:kahan@informatik.tu-muenchen.de) for

# sending the correct chat script for the passwd program in Debian Sarge).

passwd program = /usr/bin/passwd %u  
passwd chat = _Enter\snew\sUNIX\spassword:_ %n\n _Retype\snew\sUNIX\spassword:_ %n\n _password\supdated\ssuccessfully_ .

# This boolean controls whether PAM will be used for password changes

# when requested by an SMB client instead of the program listed in

# ‘passwd program’. The default is ‘no’.

; pam password change = no

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC

# must have this setting enabled. If you are the BDC you must

# change the ‘domain master’ setting to no

# 

; domain logons = yes

# 

# The following setting only takes effect if ‘domain logons’ is set

# It specifies the location of the user’s profile directory

# from the client point of view)

# The following required a [profiles] share to be setup on the

# samba server (see below)

; logon path = \%N\profiles%U

# Another common choice is storing the profile in the user’s home directory

; logon path = \%N%U\profile

# The following setting only takes effect if ‘domain logons’ is set

# It specifies the location of a user’s home directory (from the client

# point of view)

; logon drive = H:  
; logon home = \%N%U

# The following setting only takes effect if ‘domain logons’ is set

# It specifies the script to run during logon. The script must be stored

# in the [netlogon] share

# NOTE: Must be store in ‘DOS’ file format convention

; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR

# RPC pipe. The example command creates a user account with a disabled Unix

# password; please adapt to your needs

; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos “” %u

########## Printing ##########

# If you want to automatically load your printer list rather

# than setting them up individually then you’ll need this

; load printers = yes

# lpr(ng) printing. You may wish to override the location of the

# printcap file

; printing = bsd  
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the

# cupsys-client package.

; printing = cups  
; printcap name = cups

# When using [print$], root is implicitly a ‘printer admin’, but you can

# also give this right to other users to add drivers and set printer

# properties

; printer admin = @ntadmin

############ Misc ############

# Using the following line enables you to customise your configuration

# on a per machine basis. The %m gets replaced with the netbios name

# of the machine that is connecting

; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.

# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html

# for details

# You may want to add the following on a Linux system:

# SO\_RCVBUF=8192 SO\_SNDBUF=8192

# socket options = TCP\_NODELAY

# The following parameter is useful only if you have the linpopup package

# installed. The samba maintainer and the linpopup maintainer are

# working to ease installation and configuration of linpopup and samba.

; message command = /bin/sh -c ‘/usr/bin/linpopup “%f” “%m” %s; rm %s’ &

# Domain Master specifies Samba to be the Domain Master Browser. If this

# machine will be configured as a BDC (a secondary logon server), you

# must set this to ‘no’; otherwise, the default behavior is recommended.

domain master = auto

# Some defaults for winbind (make sure you’re not using the ranges

# for something else.)

; idmap uid = 10000-20000  
; idmap gid = 10000-20000  
; template shell = /bin/bash  
;  
; The following was the default behaviour in sarge  
; but samba upstream reverted the default because it might induce  
; performance issues in large organizations  
; See #368251 for some of the consequences of _not_ having  
; this setting and smb.conf(5) for all details  
;  
; winbind enum groups = yes  
; winbind enum users = yes

#======================= Share Definitions =======================

[partage]

# comment = partage de fichiers

# path = /home/asap74

# browseable = yes

# writable = yes

# public = no

# By default, the home directories are exported read-only. Change next

# parameter to ‘yes’ if you want to be able to write to them.

writable = no

# File creation mask is set to 0700 for security reasons. If you want to

# create files with group=rw permissions, set next parameter to 0775.

create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to

# create dirs. with group=rw permissions, set next parameter to 0775.

directory mask = 0700

# Restrict access to home directories

# to the one of the authenticated user

# This might need tweaking when using external authentication schemes

valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons

# (you need to configure Samba to act as a domain controller too.)

;[netlogon]  
; comment = Network Logon Service  
; path = /home/samba/netlogon  
; guest ok = yes  
; writable = no  
; share modes = no

# Un-comment the following and create the profiles directory to store

# users profiles (see the “logon path” option above)

# (you need to configure Samba to act as a domain controller too.)

# The path below should be writable by all users so that their

# profile directory may be created the first time they log on

;[profiles]  
; comment = Users profiles  
; path = /home/samba/profiles  
; guest ok = no  
; browseable = no  
; create mask = 0600  
; directory mask = 0700

[printers]  
comment = All Printers  
browseable = no  
path = /var/spool/samba  
printable = yes  
public = no  
writable = no  
create mode = 0700

# Windows clients look for this share name as a source of downloadable

# printer drivers

[print$]  
comment = Printer Drivers  
path = /var/lib/samba/printers  
browseable = yes  
read only = yes  
guest ok = no

# Uncomment to allow remote administration of Windows print drivers.

# Replace ‘ntadmin’ with the name of the group your admin users are

# members of.

; write list = root, @ntadmin

# A sample share for sharing your CD-ROM with others.

;[cdrom]  
; comment = Samba server’s CD-ROM  
; writable = no  
; locking = no  
; path = /cdrom  
; public = yes

# The next two parameters show how to auto-mount a CD-ROM when the

# cdrom share is accesed. For this to work /etc/fstab must contain

# an entry like this:

# 

# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0

# 

# The CD-ROM gets unmounted automatically after the connection to the

# 

# If you don’t want to use auto-mounting/unmounting make sure the CD

# is mounted on /cdrom

# 

; preexec = /bin/mount /cdrom  
; postexec = /bin/umount /cdrom

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/42 "2016-02-20T18:51:28Z")

</div>

étonnant ce problème avec ton routeur …  
au moins tu en as profité pour retrouver sa conf, quelle est la plage d’adresse allouée au dhcp ?

je vais regarder la conf samba, en attendant tu disposes de la commande testparm (sans arguments) qui va faire un check de ta config samba.

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/43 "2016-02-20T18:51:28Z")

</div>

```auto
# section globale
[global]
# Identification Netbios
workgroup = MYGROUP
netbios name = samba
# Controle de domaine desactive
os level = 40
domain logons = no
domain master = no
local master = no
# Base de donnee de comptes
passdb backend = tdbsam:/var/lib/samba/mypassdb.tdb (vérifie bien que le fichier existe et est à cet emplacement)
# Authentification via la base de comptes locale
security = user
# Securite
encrypt passwords = yes
# Gestion des logs
log file = /var/log/samba/%m.log
log level = 2
# sections propres à chaque partage 
[partage]
comment = dossier partage
path = /home/asap74
browseable = Yes
writeable = Yes
public = No
```

puis valider la conf avec

```auto

```

puis restart de samba

```auto

```

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/44 "2016-02-20T18:51:29Z")

</div>

dans ton fichier smb.conf, j’ai changé "mypassdb.tdb pour passdb.tdb car c’est ce fichier qui existait, c’est comme ça qu’il fallait bien faire?  
je vais maintenant essayé  
A+

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/45 "2016-02-20T18:51:29Z")

</div>

oupss…  
sur XP, je clique sur " voir les ordinateurs de mon group, la réponse est après longue attente: Mygroup n’est pas accessible, ou vous ne disposez pas des droits…

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/46 "2016-02-20T18:51:29Z")

</div>

dans la barre de recherche de Windows, tapes \samba

edit : voile voile voile ? vu ton pseudo je pensais à la haute savoie (74)… et donc à montagne montagne montagne .

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/47 "2016-02-20T18:51:30Z")

</div>

OK j’atteins l’environnement partagé du serveur  
Bon début !!  
J’ai lu dans la doc de l’application à tester, il fallait utiliser SSH pour communiquer depuis client vers serveur.

Quand je lance Secure shell Client en indiquant le nom du serveur: Debian-server ou samba, le host n’est pas reconnu, il est unreachable. Tu as une idée?

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/48 "2016-02-20T18:51:30Z")

</div>

le nom de machine samba est un nom netbios, il n’est utilisable que pour le partage de dossiers avec le serveur samba.

pour ssh il faut un nom dns ou un adresse ip. ton serveur est encore en dhcp. donc il faut que tu recupere son adresse ip par un ‘ifconfig eth0’ sur la console.

quand tu auras recuperé les infos sur la plage dhcp dans ton routeur on pourra le mettre en ip fixe.

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/49 "2016-02-20T18:51:40Z")

</div>

la plage DHCP du routeur: 192.168.1.2 192.168.1.196

Dors bien

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/50 "2016-02-20T18:51:43Z")

</div>

ok. tu va ‘enfin’ pouvoir passer ton serveur en ip fixe. ça va te simplifier la vie pour les accès via ssh et le navigateur web.  
tu mets dans /etc/network/interfaces

```auto
auto eth0
iface eth0 inet static
adress 192.168.1.200
netmask 255.255.255.0
gateway 192.168.1.1
```

à la place de

```auto
auto eth0
iface eth0 inet dhcp
```

tu valid ela configuration dns, le fichier /etc/resolv.conf doit contenir

```auto

```

ensuite

```auto

```

puis

```auto

```

devrait te configmer la nouvelle adresse ip  
tu pourras maintenent te connecter au serveur en ssh ou http en utilisant l’adresse ip 192.168.1.200

---

<div class="post-metadata">

**Author:** ![kna](https://www.debian-fr.org/user_avatar/www.debian-fr.org/kna/32/5623_2.png) [@kna](https://www.debian-fr.org/u/kna)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/51 "2016-02-20T18:51:44Z")

</div>

Sinon, tu dois pouvoir configurer ton routeur pour qu’il attribue toujours la même IP à ton serveur (en reconnaissant l’adresse MAC de ta carte réseau, que tu obtiens avec ifconfig).

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/52 "2016-02-20T18:51:45Z")

</div>

désolé de te décevoir sans doute, mais ça ne marche pas:  
debian-server:/etc# ifconfig eth0  
eth0 Lien encap:Ethernet HWaddr 00:17:3F:CD:D0:47  
inet adr:192.168.1.3 Bcast:192.168.1.255 Masque:255.255.255.0  
adr inet6: fe80::217:3fff:fecd:d047/64 Scope:Lien  
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1  
RX packets:732 errors:0 dropped:0 overruns:0 frame:0  
TX packets:716 errors:0 dropped:0 overruns:0 carrier:0  
collisions:0 lg file transmission:1000  
RX bytes:466604 (455.6 KiB) TX bytes:90817 (88.6 KiB)  
Interruption:11 Adresse de base:0xec00

et depuis SSH client, Host unreachable  
et depuis Http: même chose

le ping depus XP fonctionne pourtant (ping 192.168.1.3)

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/53 "2016-02-20T18:51:45Z")

</div>

désolé de te deçevoir mais je ne te crois pas. ré-essaye la manip, sinon colles ici ton nouveau fichier interfaces mais gare à toi si tu t’es trompé ![:smt025](https://www.debian-fr.org/uploads/default/original/1X/35c6692e8ba16def63d106be1ecaa0780e5d16d3.gif). pour tester ssh et http, il faudrait au préalable installer les serveurs qui vont bien. lances les commandes suivantes sur debian:

```auto
su (suivi du mot de passe root quand on te le demandera)
aptitude update
aptitude upgrade -y
aptitude install openssh-server -y
aptitude install apache2 -y
aptitude clean
exit
```

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/54 "2016-02-20T18:51:46Z")

</div>

fichier interfaces:

# This file describes the network interfaces available on your system

# and how to activate them. For more information, see interfaces(5).

# The loopback network interface

auto lo  
iface lo inet loopback

# The primary network interface

auto eth0

iface eth0 inet static  
adress 192.168.1.200  
netmask 255.255.255.0  
gateway 192.168.1.1

~  
~  
“interfaces” 21 lines, 341 characters

fichier interfaces:

# generated by NetworkManager, do not edit!

nameserver 192.168.1.1  
nameserver 192.168.1.1

~  
~  
~  
~  
~  
~  
~  
~  
~  
~  
~  
~  
~  
~  
~  
“resolv.conf” 8 lines, 95 characters

tu me crois ou pas?

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/55 "2016-02-20T18:51:46Z")

</div>

en même temps si tu fais bêtement ce que je te dis, il faut mettre deux d à address !! 😆

il y avaitp as une erreur lors du /etc/init.d/networking restart ?

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/56 "2016-02-20T18:51:46Z")

</div>

désolé, je n’avais pas percuté, c ma faute, c ma faute, c ma plus grande faute…je ferai gaffe la prochaine fois.  
now, depuis XP, je vois le serveur avec l’adresse http mais pas depuis SSH lorsque je tape l’adresse IP du serveur dans le nom du host, je comprends pas.  
ça va, tu tiens le coup, avec moi ?

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/57 "2016-02-20T18:51:47Z")

</div>

ça va, je tiens pour l’instant, en même temps c’est dimanche, il pleut, ma femme bosse, bébé dort, …

mais au cas ou je doives te laisser tomber tu pourras en attendant quelqu’un d’autre aller faire un tour sur (entre autres)

[http://www.debian.org/doc/ddp.fr.html](http://www.debian.org/doc/ddp.fr.html)  
[http://smhteam.info/wiki/index.linux.php5?wiki=Accueil](http://smhteam.info/wiki/index.linux.php5?wiki=Accueil)

sur debian que donne ces commandes ?

`# voir si le port ssh (22) est ouvert
netstat -anl | grep 22`

`#voir si le demon ssh tourne
ps -A | grep ssh`  
essaye de lui faire faire un ssh sur lui même

```auto

```

depuis xp, essaye de lancer un telnet sur le port 22

```auto
je sais plus la commande, c'est 
telnet 192.168.1.200 22
ou
telnet 192.168.1.200:22
```

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/58 "2016-02-20T18:51:47Z")

</div>

debian-server:/home/asap74# netstat -anl | grep 22  
tcp 0 0 127.0.0.1:2208 0.0.0.0:\* LISTEN  
tcp 0 0 127.0.0.1:52216 0.0.0.0:\* LISTEN  
unix 2 [ACC] STREAM LISTENING 9225 /tmp/orbit-asap74/lin c-c36-0-6d189f331f494  
unix 3 [] STREAM CONNECTE 9622 /tmp/orbit-root/linc- c9a-0-58409a65f1182  
unix 3 [] STREAM CONNECTE 9228 /tmp/orbit-asap74/lin c-c36-0-6d189f331f494  
unix 3 [] STREAM CONNECTE 9227  
unix 3 [] STREAM CONNECTE 9224 /tmp/orbit-asap74/lin c-c13-0-1a19f521b5bba  
unix 3 [] STREAM CONNECTE 9223  
unix 2 [] DGRAM 8722  
unix 2 [] DGRAM 6222

debian-server:/home/asap74# ps -A | grep ssh  
3085 ? 00:00:00 ssh-agent

debian-server:/home/asap74# ssh 192.168.1.200  
ssh: connect to host 192.168.1.200 port 22: Connection refused

Telnet depuis XP:  
impossible d’ouvrir une connexion à L’hote, sur le port 22: échec de la connexion

---

<div class="post-metadata">

**Author:** ![thomas.leclerc](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/t/59ef9b/32.png) [@thomas.leclerc](https://www.debian-fr.org/u/thomas.leclerc)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/59 "2016-02-20T18:51:48Z")

</div>

est ce que tu as installé le serveur openssh-server sur debian ? car il n’apparaît pas ! pas de port ouvert, pas d’agent de lancé.

test avec `aptitude show openssh-server` la seconde ligne (état) indique si il est installé ou non.  
si il est installé fais `/etc/init.d/ssh start`  
sinon lance l’installation`aptitude install openssh-server -y`

---

<div class="post-metadata">

**Author:** ![asap74](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/bcef8e/32.png) [@asap74](https://www.debian-fr.org/u/asap74)\
**Post date:** [Février 20, 2016, 6:51 UTC](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471/60 "2016-02-20T18:51:48Z")

</div>

debian-server:/home/asap74# aptitude show openssh-server  
E: Erreur de lecture - read (5 Erreur d’entrée/sortie)  
E: Erreur de lecture - read (5 Erreur d’entrée/sortie)  
debian-server:/home/asap74# aptitude install openssh-server -y  
Lecture des listes de paquets… Fait  
Construction de l’arbre des dépendances… Fait  
Lecture de l’information d’état étendu  
Initialisation de l’état des paquets… Erreur !  
E: Erreur de lecture - read (5 Erreur d’entrée/sortie)  
Lecture des listes de paquets… Fait  
Construction de l’arbre des dépendances… Fait  
Lecture de l’information d’état étendu  
Initialisation de l’état des paquets… Erreur !  
E: Erreur de lecture - read (5 Erreur d’entrée/sortie)  
debian-server:/home/asap74#

[Page précédente](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471.md?page=2)

[Page suivante](https://www.debian-fr.org/t/client-xp-sur-debian-server/17471.md?page=4)
