Drucker Im Netzwerk Finden Windows 10
Netzwerkdrucker sind 'sichtbar', aber nicht nutzbar
Status: Ungelöst | Ubuntu-Version: Ubuntu 22.04 (Jammy Jellyfish)
Antworten |
| Zollstocks  Anmeldungsdatum: Beiträge: 94 Wohnort: Ostercappeln | Zitieren v. September 2022 14:19 (zuletzt bearbeitet: 5. September 2022 14:23) Moin, dpkg -l *cups* lpr* | grep two ii bluez-cups 5.64-0ubuntu1 amd64 Bluetooth printer driver for CUPS ii cups 2.iv.1op1-1ubuntu4.i amd64 Mutual UNIX Printing System(tm) - PPD/driver support, spider web interface ii cups-browsed 1.28.15-0ubuntu1 amd64 OpenPrinting CUPS Filters - cups-browsed two cups-bsd two.4.1op1-1ubuntu4.1 amd64 Common UNIX Printing Arrangement(tm) - BSD commands ii cups-client 2.4.1op1-1ubuntu4.1 amd64 Common UNIX Printing System(tm) - client programs (SysV) ii cups-common 2.iv.1op1-1ubuntu4.1 all Common UNIX Printing System(tm) - mutual files ii cups-core-drivers two.4.1op1-1ubuntu4.ane amd64 Mutual UNIX Press Arrangement(tm) - driverless press ii cups-daemon two.4.1op1-1ubuntu4.1 amd64 Common UNIX Printing System(tm) - daemon ii cups-filters 1.28.15-0ubuntu1 amd64 OpenPrinting CUPS Filters - Chief Packet ii cups-filters-core-drivers ane.28.fifteen-0ubuntu1 amd64 OpenPrinting CUPS Filters - Driverless printing ii cups-ipp-utils ii.4.1op1-1ubuntu4.1 amd64 Common UNIX Printing System(tm) - IPP developer/admin utilities ii cups-pk-helper 0.2.6-1ubuntu5 amd64 PolicyKit helper to configure cups with fine-grained privileges ii cups-ppdc 2.4.1op1-1ubuntu4.1 amd64 Mutual UNIX Printing System(tm) - PPD manipulation utilities two cups-server-common ii.four.1op1-1ubuntu4.1 all Common UNIX Printing Organisation(tm) - server mutual files ii libcups2:amd64 two.4.1op1-1ubuntu4.1 amd64 Mutual UNIX Printing Organization(tm) - Core library ii libcupsfilters1:amd64 i.28.15-0ubuntu1 amd64 OpenPrinting CUPS Filters - Shared library ii libcupsimage2:amd64 2.iv.1op1-1ubuntu4.1 amd64 Mutual UNIX Printing System(tm) - Raster image library 2 printer-driver-hpcups 3.21.12+dfsg0-1 amd64 HP Linux Printing and Imaging - CUPS Raster driver (hpcups) ii python3-cups:amd64 2.0.ane-5build1 amd64 Python3 bindings for CUPS two python3-cupshelpers 1.5.16-0ubuntu3 all Python utility modules around the CUPS printing system uwe@uwe-ThinkPad-P51:~$ dpkg -l libusb* | grep ii ii libusb-ane.0-0:amd64 two:1.0.25-1ubuntu2 amd64 userspace USB programming library ii libusbmuxd6:amd64 ii.0.2-3build2 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - library uwe@uwe-ThinkPad-P51:~$ dpkg -l | egrep Brother ii printer-driver-brlaser vi-3 amd64 printer driver for (some) Blood brother laser printers ii printer-commuter-ptouch 1.vi-2build1 amd64 printer driver Brother P-impact label printers uwe@uwe-ThinkPad-P51:~$ dpkg -fifty | egrep hp 2 hplip 3.21.12+dfsg0-1 amd64 HP Linux Printing and Imaging Arrangement (HPLIP) ii hplip-data iii.21.12+dfsg0-1 all HP Linux Printing and Imaging - data files ii libhpmud0:amd64 3.21.12+dfsg0-1 amd64 HP Multi-Point Transport Commuter (hpmud) run-time libraries ii libsane-hpaio:amd64 iii.21.12+dfsg0-1 amd64 HP SANE backend for multi-function peripherals 2 printer-commuter-hpcups 3.21.12+dfsg0-1 amd64 HP Linux Printing and Imaging - CUPS Raster driver (hpcups) ii printer-driver-postscript-hp three.21.12+dfsg0-one amd64 HP Printers PostScript Descriptions ii python3-launchpadlib 1.10.sixteen-one all Launchpad web services client library (Python iii) uwe@uwe-ThinkPad-P51:~$ dpkg -l | egrep 'iscan*|esci-*|epson' uwe@uwe-ThinkPad-P51:~$ dpkg -l | egrep 'scangear*|cnij*' $ systemctl --no-pager status cups* ● cups-browsed.service - Make remote CUPS printers bachelor locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Agile: active (running) since Mon 2022-09-05 13:59:06 CEST; 9min agone Master PID: 1311 (cups-browsed) Tasks: three (limit: 38103) Memory: v.1M CPU: 65ms CGroup: /system.piece/cups-browsed.service └─1311 /usr/sbin/cups-browsed Sep 05 13:59:06 uwe-ThinkPad-P51 systemd[one]: Started Make remote CUPS printers available locally. ● cups.path - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.path; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-09-05 thirteen:59:00 CEST; 9min ago Triggers: ● cups.service Sep 05 thirteen:59:00 uwe-ThinkPad-P51 systemd[i]: Started CUPS Scheduler. ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-09-05 13:59:00 CEST; 9min ago TriggeredBy: ● cups.path ● cups.socket Docs: human:cupsd(eight) Main PID: 804 (cupsd) Status: "Scheduler is running..." Tasks: two (limit: 38103) Memory: 6.9M CPU: 38ms CGroup: /system.slice/cups.service ├─ 804 /usr/sbin/cupsd -l └─1344 /usr/lib/cups/notifier/dbus dbus:// "" Sep 05 13:59:00 uwe-ThinkPad-P51 systemd[one]: Starting CUPS Scheduler... Sep 05 thirteen:59:00 uwe-ThinkPad-P51 systemd[one]: Started CUPS Scheduler. ● cups.socket - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.socket; enabled; vendor preset: enabled) Agile: active (running) since Mon 2022-09-05 13:59:00 CEST; 9min agone Triggers: ● cups.service Listen: /run/cups/cups.sock (Stream) CGroup: /system.slice/cups.socket Sep 05 xiii:59:00 uwe-ThinkPad-P51 systemd[1]: Listening on CUPS Scheduler. uwe@uwe-ThinkPad-P51:~$ lpstat -t Zeitplandienst läuft keine systemvoreingestellten Ziele Gerät für Kyocera_TASKalfa_3051ci: implicitclass://Kyocera_TASKalfa_3051ci/ Kyocera_TASKalfa_3051ci akzeptiert Anfragen seit Mo 05 Sep 2022 thirteen:59:37 CEST Drucker Kyocera_TASKalfa_3051ci ist im Leerlauf. Aktiviert seit Mo 05 Sep 2022 thirteen:59:37 CEST uwe@uwe-ThinkPad-P51:~$ lpinfo -v file cups-brf:/ network ipps network http network ipp serial serial:/dev/ttyS0?baud=115200 serial serial:/dev/ttyS4?baud=115200 network lpd network socket network beh network https direct hp directly hpfax network dnssd://Kyocera%20FS-2100DN._ipp._tcp.local/?uuid=4509a320-00fd-009a-0093-00251a51577a network dnssd://Kyocera%20TASKalfa%203051ci._ipps._tcp.local/?uuid=4509a320-002b-006a-00ea-0025074e97f8 network ipp://Kyocera%20FS-2100DN._ipp._tcp.local/ network ipps://Kyocera%20TASKalfa%203051ci._ipps._tcp.local/ network socket://192.168.two.109 network socket://192.168.2.nine uwe@uwe-ThinkPad-P51:~$ hp-info -i HP Linux Imaging and Printing System (ver. iii.21.12) Device Information Utility ver. 5.2 Copyright (c) 2001-eighteen HP Evolution Visitor, LP This software comes with Admittedly NO WARRANTY. This is free software, and yous are welcome to distribute it under certain weather. Come across COPYING file for more than details. mistake: No device found that back up this feature. uwe@uwe-ThinkPad-P51:~$ uname -rm 5.15.0-47-generic x86_64 uwe@uwe-ThinkPad-P51:~$ lsusb Bus 002 Device 003: ID 17ef:305b Lenovo Lenovo ThinkPad WS Dock Motorcoach 002 Device 002: ID 17ef:305a Lenovo Lenovo ThinkPad WS Dock Double-decker 002 Device 001: ID 1d6b:0003 Linux Foundation iii.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ab Chicony Electronics Co., Ltd Integrated Photographic camera Bus 001 Device 006: ID 17ef:305b Lenovo Lenovo ThinkPad WS Dock Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Coach 001 Device 002: ID 17ef:305a Lenovo Lenovo ThinkPad WS Dock Bus 001 Device 009: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 008: ID 0765:5010 X-Rite, Inc. X-Rite Pantone Color Sensor Bus 001 Device 007: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Autobus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub uwe@uwe-ThinkPad-P51:~$ id uid=1000(uwe) gid=m(uwe) Gruppen=1000(uwe),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),122(lpadmin),134(lxd),135(sambashare) uwe@uwe-ThinkPad-P51:~$ ls -l /etc/cups/ppd/* -rw-r----- 1 root lp 14128 Sep 5 13:59 /etc/cups/ppd/Kyocera_TASKalfa_3051ci.ppd Mein Problem: wenn ich drucken will, sind dice Drucker im Netzwerk zwar sichtbar, aber nicht nutzbar. Entweder wird dice Data geleiefert, das der Drucker nicht antwortet oder der Druckauftrag bleibt für ewig im Spooler. Wie löse ich das Problem? |
| Zollstocks (Themenstarter) Anmeldungsdatum: Beiträge: 94 Wohnort: Ostercappeln | Zitieren thirteen. September 2022 15:47 schubs... |
| Webmark  Anmeldungsdatum: Beiträge: 294 | Zitieren thirteen. September 2022 15:59 Mein Netzwerkdrucker wird nach einer Neuinstallation auch erkannt, dennoch ist drucken erst möglich nachdem ich unter Zusätzliche Druckereinstellungen - eben den Netzwerkdrucker anzeigen lasse und im nächsten Schritt die entsprechenden Treiber installiere. Eventuell hilft dir dies weiter? |
| Zollstocks (Themenstarter) Anmeldungsdatum: Beiträge: 94 Wohnort: Ostercappeln | Zitieren xv. September 2022 11:12 Leider nein. Ich arbeite an zwei unterschiedlichen Arbeitsplätzen, beide mit einem kleinen Netzwerk über eine Fritz-Box. Beim einen Platz kann ich auf die Drucker zugreifen, beim anderen nicht. Kann es eine Einstellung der Fritz-Box sein, die mich hier ausbremst? Hier meine smb.conf: # # 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 # # Some options that are often worth tuning accept been included every bit # commented-out examples in this file. # - When such options are commented with ";", the proposed setting # differs from the default Samba behaviour # - When commented with "#", the proposed setting is the default # behaviour of Samba but the selection is considered important # plenty to be mentioned here # # NOTE: Whenever you modify this file yous should run the command # "testparm" to bank check that you have not fabricated any basic syntactic # errors. #======================= Global Settings ======================= [global] ## Browsing/Identification ### # Alter this to the workgroup/NT-domain name your Samba server will office of workgroup = WORKGROUP # server string is the equivalent of the NT Description field server cord = %h server (Samba, Ubuntu) #### Networking #### # The specific set of interfaces / networks to bind to # This tin can be either the interface name or an IP address/netmask; # interface names are unremarkably preferred ; interfaces = 127.0.0.0/viii eth0 # Merely demark to the named interfaces and/or networks; you must use the # 'interfaces' option above to utilise this. # Information technology is recommended that you enable this feature if your Samba machine is # not protected past a firewall or is a firewall itself. However, this # option cannot handle dynamic or non-circulate interfaces correctly. ; demark interfaces only = yeah #### Debugging/Accounting #### # This tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Cap the size of the individual log files (in KiB). max log size = 1000 # We desire Samba to only log to /var/log/samba/log.{smbd,nmbd}. # Append syslog@1 if y'all want of import messages to be sent to syslog likewise. logging = file # Do something sensible when Samba crashes: mail the admin a backtrace panic activity = /usr/share/samba/panic-activeness %d ####### Authentication ####### # Server role. Defines in which fashion Samba will operate. Possible # values are "standalone server", "member server", "classic primary # domain controller", "archetype fill-in domain controller", "active # directory domain controller". # # Near people will want "standalone server" or "fellow member server". # Running every bit "active directory domain controller" will require first # running "samba-tool domain provision" to wipe databases and create a # new domain. server function = standalone server obey pam restrictions = yes # This boolean parameter controls whether Samba attempts to sync the Unix # password with the SMB password when the encrypted SMB countersign in the # passdb is changed. unix countersign sync = yes # For Unix password sync to work on a Debian GNU/Linux system, the following # parameters must be set (cheers to Ian Kahan <<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 conversation = *Enter\snew\s*\spassword:* %northward\north *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . # This boolean controls whether PAM volition be used for password changes # when requested past an SMB client instead of the program listed in # 'passwd plan'. The default is 'no'. pam countersign change = aye # This pick controls how unsuccessful authentication attempts are mapped # to anonymous connections map to invitee = bad user ########## Domains ########### # # The following settings only takes effect if 'server role = classic # main domain controller', 'server office = classic backup domain controller' # or 'domain logons' is prepare # # It specifies the location of the user's # contour directory from the client point of view) The post-obit # required a [profiles] share to be setup on the samba server (encounter # below) ; logon path = \\%N\profiles\%U # Another mutual choice is storing the profile in the user's dwelling directory # (this is Samba'south default) # logon path = \\%Due north\%U\contour # The following setting only takes effect if 'domain logons' is gear up # It specifies the location of a user'southward home directory (from the client # indicate of view) ; logon drive = H: # logon home = \\%N\%U # The following setting only takes outcome if 'domain logons' is set # It specifies the script to run during logon. The script must exist stored # in the [netlogon] share # Notation: Must exist store in 'DOS' file format convention ; logon script = logon.cmd # This allows Unix users to exist created on the domain controller via the SAMR # RPC pipe. The case control creates a user account with a disabled Unix # password; please accommodate to your needs ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u # This allows car accounts to be created on the domain controller via the # SAMR RPC piping. # The following assumes a "machines" group exists on the organisation ; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/imitation %u # This allows Unix groups to be created on the domain controller via the SAMR # RPC pipe. ; add group script = /usr/sbin/addgroup --force-badname %g ############ Misc ############ # Using the following line enables y'all to customise your configuration # on a per machine footing. The %m gets replaced with the netbios proper noun # of the machine that is connecting ; include = /home/samba/etc/smb.conf.%m # Some defaults for winbind (make sure you're not using the ranges # for something else.) ; idmap config * : backend = tdb ; idmap config * : range = 3000-7999 ; idmap config YOURDOMAINHERE : backend = tdb ; idmap config YOURDOMAINHERE : range = 100000-999999 ; template shell = /bin/bash # Setup usershare options to enable non-root users to share folders # with the net usershare command. # Maximum number of usershare. 0 means that usershare is disabled. # usershare max shares = 100 # Allow users who've been granted usershare privileges to create # public shares, non but authenticated ones usershare allow guests = yes #======================= Share Definitions ======================= # United nations-annotate the following (and tweak the other settings below to suit) # to enable the default domicile directory shares. This will share each # user'due south home directory as \\server\username ;[homes] ; comment = Home Directories ; browseable = no # By default, the home directories are exported read-only. Change the # next parameter to 'no' if y'all want to be able to write to them. ; read only = yes # File creation mask is set to 0700 for security reasons. If you desire to # create files with group=rw permissions, set next parameter to 0775. ; create mask = 0700 # Directory creation mask is ready to 0700 for security reasons. If you want to # create dirs. with group=rw permissions, set next parameter to 0775. ; directory mask = 0700 # By default, \\server\username shares tin exist continued to by anyone # with admission to the samba server. # Un-comment the following parameter to make sure that merely "username" # can connect to \\server\username # This might need tweaking when using external authentication schemes ; valid users = %Southward # Un-comment the following and create the netlogon directory for Domain Logons # (y'all need to configure Samba to human action as a domain controller too.) ;[netlogon] ; comment = Network Logon Service ; path = /home/samba/netlogon ; guest ok = yes ; read only = yes # Un-annotate the post-obit and create the profiles directory to store # users profiles (see the "logon path" selection above) # (you need to configure Samba to act equally a domain controller also.) # The path below should exist writable past all users so that their # profile directory may exist created the first fourth dimension they log on ;[profiles] ; annotate = Users profiles ; path = /home/samba/profiles ; invitee ok = no ; browseable = no ; create mask = 0600 ; directory mask = 0700 [printers] annotate = All Printers browseable = no path = /var/spool/samba printable = yes guest ok = no read only = yes create mask = 0700 # Windows clients look for this share name as a source of downloadable # printer drivers [impress$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yep read merely = yes guest ok = no # Uncomment to allow remote assistants of Windows print drivers. # You lot may need to replace 'lpadmin' with the proper name of the group your # admin users are members of. # Delight note that you likewise demand to set appropriate Unix permissions # to the drivers directory for these users to have write rights in it ; write listing = root, @lpadmin |
| kB Supporter  Anmeldungsdatum: Beiträge: 6729 Wohnort: Münster | Zitieren 15. September 2022 11:32 Zollstocks schrieb:
Die natürlich unterschiedlich konfiguriert sein können. Zeige bitte von beiden jeweils die Ausgaben dieser Befehle: hostname uname -a apt policy cups lpstat -t
Was heißt das? Hat jeder Arbeitsplatz eine eigene Fritzbox oder gibt es eine gemeinsame Fritzbox? Wo und wie ist der Netzwerkdrucker an das Gesamtsystem angeschlossen? |
| Zollstocks (Themenstarter) Anmeldungsdatum: Beiträge: 94 Wohnort: Ostercappeln | Zitieren 15. September 2022 11:40 kB schrieb:
Hier der Arbeitsplatz mit den Problemen: hostname uwe-ThinkPad-P51 uwe@uwe-ThinkPad-P51:~$ uname -a Linux uwe-ThinkPad-P51 v.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux uwe@uwe-ThinkPad-P51:~$ apt policy cups cups: Installiert: two.iv.1op1-1ubuntu4.1 Installationskandidat: two.four.1op1-1ubuntu4.1 Versionstabelle: *** 2.iv.1op1-1ubuntu4.1 500 500 http://cc.annal.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/primary amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://cc.archive.ubuntu.com/ubuntu jammy/master amd64 Packages uwe@uwe-ThinkPad-P51:~$ lpstat -t Zeitplandienst läuft keine systemvoreingestellten Ziele Gerät für Kyocera_TASKalfa_3051ci: dnssd://Kyocera%20TASKalfa%203051ci._ipps._tcp.local/?uuid=4509a320-002b-006a-00ea-0025074e97f8 Kyocera_TASKalfa_3051ci akzeptiert Anfragen seit Do fifteen Sep 2022 ten:34:thirteen CEST Drucker Kyocera_TASKalfa_3051ci ist im Leerlauf. Aktiviert seit Do fifteen Sep 2022 10:34:xiii CEST Sleeping... von anderen Platz kann ich im Moment keine Informationen liefern, denn:
jeder Platz hat eine eigene FritzBox - die beiden Plätze (einmal Daheim, einmal Büro) liegen gut xxx km voneinander entfernt...
Es sind hier zwei Drucker, die beide über Lan im System angeschlossen sind. Die Drucker sind nicht direkt an einen Rechner angeschlossen. |
| kB Supporter Anmeldungsdatum: Beiträge: 6729 Wohnort: Münster | Zitieren 15. September 2022 12:eleven Zollstocks schrieb:
In diesem Fall ist natürlich bedeutsam, wie die beiden Fritzboxen miteinander gekoppelt sind, ob beide als eigenständige Endpunkte im Internet arbeiten oder per VPN zu einem gemeinsamen Netzwerk gehören, wie die Firewalls konfiguriert sind usw. |
| Zollstocks (Themenstarter) Anmeldungsdatum: Beiträge: 94 Wohnort: Ostercappeln | Zitieren fifteen. September 2022 12:37 kB schrieb:
Die sind gar nicht miteinander gekoppelt. Jede Box ist eigenständig. |
| kB Supporter Anmeldungsdatum: Beiträge: 6729 Wohnort: Münster | Zitieren 15. September 2022 14:41 Zollstocks schrieb:
Und wie siehst Du dann aus dem Netz hinter Fritzbox A die Drucker im Netz hinter Fritzbox B? |
| Zollstocks (Themenstarter) Anmeldungsdatum: Beiträge: 94 Wohnort: Ostercappeln | Zitieren 15. September 2022 14:48 kB schrieb:
gar nicht... Ich hatte mich wohl irgendwo weiter oben mißverständlich ausgedrückt. Darum drösel ich das mal auf:
Die beiden FritzBoxen haben keine Verbindung. Das einzige gemeinsame Teil ist mein Laptop. |
| kB Supporter Anmeldungsdatum: Beiträge: 6729 Wohnort: Münster | Zitieren xv. September 2022 16:xiv Zollstocks schrieb:
In dem Fall musst Du natürlich auf dem Laptop für die beiden Drucker daheim jeweils eine Warteschlange einrichten und für die beiden Drucker im Büro jeweils eine weitere Warteschlange, insgesamt also 4. Du kannst eine Warteschlange für daheim nicht im Büro benutzen und umgekehrt, selbst wenn dice physischen Drucker baugleich sein sollten. Du kannst aber zusätzlich eine Warteschlange für daheim und eine Warteschlange für das Büro zu einer Klasse zusammenfassen und an beiden Orten auf diese Klasse drucken; CUPS sollte dann selbst jeweils den verfügbaren Drucker finden. |
| Zollstocks (Themenstarter) Anmeldungsdatum: Beiträge: 94 Wohnort: Ostercappeln | Zitieren nineteen. September 2022 08:01 kB schrieb:
Ich vermute, Du vernutest etwas zu komplizert... Ich habe zwei getrennte Arbeitsplätze, halt einen daheim und einen im Büro. Da packe ich meinen Laptop in dice Dockingstation und fertig (ok, Wunschzustand...) Daheim ist das leben wunderbar, ich kann die beiden Drucker nutzen. Im Büro halt leider nicht. |
| lubux Anmeldungsdatum: Beiträge: 12612 | Zitieren 19. September 2022 x:03 Zollstocks schrieb:
Wie ist im Büro, an deinem Laptop die Ausgabe von: ip neighbor show ? |
| Zollstocks (Themenstarter) Anmeldungsdatum: Beiträge: 94 Wohnort: Ostercappeln | Zitieren 19. September 2022 x:26 ip neighbor bear witness 192.168.2.109 dev enp0s31f6 lladdr 00:c0:ee:d8:75:6e Stale 192.168.2.1 dev wlp4s0 lladdr 74:42:7f:39:24:45 STALE 192.168.two.i dev enp0s31f6 lladdr 74:42:7f:39:24:45 REACHABLE 192.168.2.30 dev enp0s31f6 lladdr 14:b3:1f:03:f8:18 Stale |
| lubux Anmeldungsdatum: Beiträge: 12612 | Zitieren 19. September 2022 10:42 Zollstocks schrieb: ip neighbor show 192.168.2.109 dev enp0s31f6 lladdr 00:c0:ee:d8:75:6e STALE 192.168.2.ane dev wlp4s0 lladdr 74:42:7f:39:24:45 Dried 192.168.2.ane dev enp0s31f6 lladdr 74:42:7f:39:24:45 REACHABLE 192.168.two.30 dev enp0s31f6 lladdr fourteen:b3:1f:03:f8:eighteen STALE Du benutzt lan- und wlan-Verbindung gleichzeitig. Sind die IPs .30 und .109 dice Drucker? Wie sind die Ausgaben von: route -north ip route get 192.168.two.30 ip route get 192.168.2.109 ping -c 3 192.168.2.thirty ? Wenn Du drucken willst und es nicht funktioniert, kommt dann Traffic zwischen Laptop und Druckern zustande? sudo tcpdump -c 300 -vvveni any host 192.168.2.30 or host 192.168.ii.109 ? |
Drucker Im Netzwerk Finden Windows 10,
Source: https://forum.ubuntuusers.de/post/9337671/
Posted by: adcockfibine.blogspot.com
0 Response to "Drucker Im Netzwerk Finden Windows 10"
Post a Comment