Hydra error could not resolve address - Исправление ошибок и поиск оптимальных решений проблем

Hydra v8.8 (c) 2019 by van Hauser/THC - Please do not use in military or secret service organizations, or for illegal purposes.




[DEBUG] Output color flag is 1
Hydra (https://github.com/vanhauser-thc/thc-hydra) starting at 2019-05-16 07:59:08
[DEBUG] cmdline: hydra -O -v -d -l name -p pass -m /:authUserLogin=^USER^&authUserPass=^PASS^:Отказано в доступе https-post-form://example.ru:443
[DEBUG] opt:10 argc:11 mod:https-post-form tgt:example.ru port:443 misc:/:authUserLogin=^USER^&authUserPass=^PASS^:Отказано в доступе
[WARNING] Restorefile (you have 10 seconds to abort... (use option -I to skip waiting)) from a previous session found, to prevent overwriting, ./hydra.restore
[DATA] max 1 task per 1 server, overall 1 task, 1 login try (l:1/p:1), ~1 try per task
[DATA] attacking http-post-forms://example.ru:443/:authUserLogin=^USER^&authUserPass=^PASS^:Отказано в доступе
[VERBOSE] Resolving addresses ...
[DEBUG] resolving example.ru
[VERBOSE] resolving done
[DEBUG] Code: attack   Time: 1557993558
[DEBUG] Options: mode 0  ssl 1  restore 0  showAttempt 0  tasks 1  max_use 1 tnp 0  tpsal 0  tprl 0  exit_found 0  miscptr /:authUserLogin=^USER^&authUserPass=^PASS^:Отказано в доступе  service http-post-form
[DEBUG] Brains: active 0  targets 1  finished 0  todo_all 1  todo 1  sent 0  found 0  countlogin 1  sizelogin 11  countpass 1  sizepass 5
[DEBUG] Target 0 - target example.ru  ip 185.132.163.137  login_no 0  pass_no 0  sent 0  pass_state 0  redo_state 0 (0 redos)  use_count 0  failed 0  done 0  fail_count 0  login_ptr name  pass_ptr pass
[DEBUG] Task 0 - pid 0  active 0  redo 0  current_login_ptr (null)  current_pass_ptr (null)
[DEBUG] Tasks 1 inactive  0 active
[DEBUG] child 0 got target 0 selected
[DEBUG] child 0 spawned for target 0 with pid 3354
[DEBUG] head_no 0 has pid 3354
[DEBUG] head_no[0] read n
[DEBUG] send_next_pair_init target 0, head 0, redo 0, redo_state 0, pass_state 0. loop_mode 0, curlogin (null), curpass (null), tlogin name, tpass pass, logincnt 0/1, passcnt 0/1, loop_cnt 1
[DEBUG] send_next_pair_mid done 1, pass_state 0, clogin name, cpass pass, tlogin -p, tpass pass, redo 0
[ATTEMPT] target example.ru - login "name" - pass "pass" - 1 of 1 [child 0] (0/0)
DEBUG_CONNECT_OK
[VERBOSE] Could not create an SSL session: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol
[ERROR] Child with pid 3354 terminating, cannot connect
[DEBUG] pid 3354 called child_exit with code 1
[DEBUG] head_no[0] read C
[ATTEMPT-ERROR] target example.ru - login "name" - pass "pass" - child 0 - 1 of 1
[DEBUG] hydra_increase_fail_count: 1 >= 0 => disable
[DEBUG] - will be retried at the end: ip example.ru - login name - pass pass - child 0
[DEBUG] head_no 0, kill 1, fail 0
[DEBUG] child 0 got target 0 selected
[DEBUG] child 0 spawned for target 0 with pid 3355
[DEBUG] head_no 0 has pid 3355
[DEBUG] head_no[0] read n
[DEBUG] send_next_pair_init target 0, head 0, redo 1, redo_state 0, pass_state 0. loop_mode 0, curlogin , curpass , tlogin -p, tpass a480, logincnt 1/1, passcnt 0/1, loop_cnt 1
[COMPLETED] target example.ru - login "" - pass "" - child 0 - 1 of 2
[DEBUG] send_next_pair_mid done 0, pass_state 0, clogin , cpass , tlogin -p, tpass pass, redo 1
[DEBUG] Entering redo_state
[DEBUG] send_next_pair_init target 0, head 0, redo 1, redo_state 1, pass_state 0. loop_mode 0, curlogin , curpass , tlogin -p, tpass a480, logincnt 1/1, passcnt 0/1, loop_cnt 2
[COMPLETED] target example.ru - login "" - pass "" - child 0 - 1 of 2
[DEBUG] send_next_pair_mid done 1, pass_state 0, clogin name, cpass pass, tlogin -p, tpass pass, redo 1
[REDO-ATTEMPT] target example.ru - login "name" - pass "pass" - 2 of 2 [child 0] (1/1)
DEBUG_CONNECT_OK
[VERBOSE] Could not create an SSL session: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol
[ERROR] Child with pid 3355 terminating, cannot connect
[DEBUG] pid 3355 called child_exit with code 1
[DEBUG] head_no[0] read C
[ATTEMPT-ERROR] target example.ru - login "name" - pass "pass" - child 0 - 2 of 1
[DEBUG] hydra_increase_fail_count: 2 >= 0 => disable
[DEBUG] - will be retried at the end: ip ks.rsmu.ru - login makarov_pa - pass a480 - child 0
[DEBUG] head_no 0, kill 1, fail 0
[DEBUG] child 0 got target 0 selected
[DEBUG] child 0 spawned for target 0 with pid 3356
[DEBUG] head_no 0 has pid 3356
[DEBUG] head_no[0] read n
[DEBUG] send_next_pair_init target 0, head 0, redo 2, redo_state 2, pass_state 0. loop_mode 0, curlogin , curpass , tlogin -p, tpass a480, logincnt 1/1, passcnt 0/1, loop_cnt 1
[COMPLETED] target example.ru - login "" - pass "" - child 0 - 2 of 3
[DEBUG] send_next_pair_mid done 1, pass_state 0, clogin makarov_pa, cpass a480, tlogin -p, tpass a480, redo 2
[REDO-ATTEMPT] target example.ru - login "name" - pass "pass" - 3 of 3 [child 0] (2/2)
DEBUG_CONNECT_OK
[VERBOSE] Could not create an SSL session: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol
[ERROR] Child with pid 3356 terminating, cannot connect
[DEBUG] pid 3356 called child_exit with code 1
[DEBUG] head_no[0] read C
[ATTEMPT-ERROR] target example.ru - login "name" - pass "pass" - child 0 - 3 of 1
[DEBUG] hydra_increase_fail_count: 3 >= 0 => disable
[DEBUG] - will be retried at the end: ip example.ru - login name - pass pass - child 0
[DEBUG] head_no 0, kill 1, fail 0
[DEBUG] child 0 got target 0 selected
[DEBUG] child 0 spawned for target 0 with pid 3358
[DEBUG] head_no 0 has pid 3358
[DEBUG] head_no[0] read n
[DEBUG] send_next_pair_init target 0, head 0, redo 3, redo_state 3, pass_state 0. loop_mode 0, curlogin , curpass , tlogin -p, tpass a480, logincnt 1/1, passcnt 0/1, loop_cnt 1
[COMPLETED] target ks.rsmu.ru - login "" - pass "" - child 0 - 3 of 4
[DEBUG] send_next_pair_mid done 1, pass_state 0, clogin makarov_pa, cpass a480, tlogin -p, tpass a480, redo 3
[REDO-ATTEMPT] target ks.rsmu.ru - login "name" - pass "pass" - 4 of 4 [child 0] (3/3)
DEBUG_CONNECT_OK
[VERBOSE] Could not create an SSL session: error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol
[ERROR] Child with pid 3358 terminating, cannot connect
[DEBUG] pid 3358 called child_exit with code 1
[DEBUG] head_no[0] read C
[ATTEMPT-ERROR] target ks.rsmu.ru - login "name" - pass "pass" - child 0 - 4 of 1
[DEBUG] hydra_increase_fail_count: 4 >= 0 => disable
[DEBUG] head_no 0, kill 1, fail 0
[DEBUG] child 0 got target 0 selected
[DEBUG] child 0 spawned for target 0 with pid 3359
[DEBUG] head_no 0 has pid 3359
[DEBUG] head_no[0] read n
[STATUS] attack finished for example.ru (waiting for children to complete tests)
[DEBUG] head_no 0, kill 1, fail 0
[DEBUG] all targets done and all heads finished
[DEBUG] while loop left with 1
1 of 1 target completed, 0 valid passwords found
[DEBUG] killing all remaining children now that might be stuck

Источник

Как правильно задавать вопросы

Правильно сформулированный вопрос и его грамотное оформление способствует высокой вероятности получения достаточно содержательного и по существу ответа. Общая рекомендация по составлению тем: 1. Для начала воспользуйтесь поиском форума. 2. Укажите версию ОС вместе с разрядностью. Пример: LM 19.3 x64, LM Sarah x32 3. DE. Если вопрос касается двух, то через запятую. (xfce, KDE, cinnamon, mate) 4. Какое железо. (достаточно вывод inxi -Fxz в спойлере (как пользоваться спойлером смотрим здесь)) или же дать ссылку на hw-probe 5. Суть. Желательно с выводом консоли, логами. 6. Скрин. Просьба указывать 2, 3 и 4 независимо от того, имеет ли это отношение к вопросу или нет. Так же не забываем об общих правилах Как пример вот

Anatol: Сообщения: 15; Зарегистрирован: 15 май 2017, 21:08; Благодарил (а): 2 раза; Контактная информация:

Ошибка при монтировании по сети

15 май 2017, 21:17

Здравствуйте. Дано — линукс машина, виндовая шара (ip-динамический). Настраиваю автоматическое монтирование при загрузке через ИМЯ компьютера, не ip. Не монтирует. при попытке монтировать вручную выдает : mount error could not resolve address for «server name» unknown error. Куда копать? nsswitch.conf есть строчка hosts: files mdns4_minimal [NOTFOUND=return] wins dns mdns4

Последний раз редактировалось пользователем 1 Dja; всего редактировалось раз: 18

Причина: подправил название

di_mok: Сообщения: 5440; Зарегистрирован: 27 авг 2016, 19:06; Решено: 32; Откуда: Арзамас; Благодарил (а): 1569 раз; Поблагодарили: 1263 раза; Контактная информация:

mount error could not resolve address

15 май 2017, 21:38

Anatol, а по имени пингуется?

Настоящая водка — это не пьянство, а ключ к своей совести, с нее-то и начинается настоящая мудрость. (c)

Anatol: Сообщения: 15; Зарегистрирован: 15 май 2017, 21:08; Благодарил (а): 2 раза; Контактная информация:

mount error could not resolve address

16 май 2017, 07:00

Не пробовал, завтра попробую, выходной сегодня. По ip всё монтирует кстати, все прекрасно работает.

upd. забыл версию написать 18.1 mate

Anatol: Сообщения: 15; Зарегистрирован: 15 май 2017, 21:08; Благодарил (а): 2 раза; Контактная информация:

mount error could not resolve address

17 май 2017, 13:21

по имени не пингуется (если я правильно пиингую — ping имя_компьютера?) Сеть без домена. небольшая локалка.
upd. Неужели нет решения попроще, через граф оболчку, ткнул мышью — примонтировал навсегда…..

Unborn: Сообщения: 1920; Зарегистрирован: 03 сен 2016, 13:36; Решено: 24; Благодарил (а): 5 раз; Поблагодарили: 264 раза; Контактная информация:

mount error could not resolve address

17 май 2017, 13:57

Anatol писал(а): Настраиваю автоматическое монтирование при загрузке через ИМЯ компьютера, не ip.

Буквы в цифры кто у тебя будет преобразовывать? Или как понять?

Anatol: Сообщения: 15; Зарегистрирован: 15 май 2017, 21:08; Благодарил (а): 2 раза; Контактная информация:

mount error could not resolve address

17 май 2017, 15:08

не понял про буквы в цифры…..

Chocobo: Сообщения: 9954; Зарегистрирован: 27 авг 2016, 22:57; Решено: 214; Откуда: НН; Благодарил (а): 795 раз; Поблагодарили: 2980 раз; Контактная информация:

mount error could not resolve address

17 май 2017, 15:49

речь о том, что при сетевом монтировании используются dns-имена (грубо говоря), которые преобразуются в ip
На какой ip стучаться клиенту до сервера, когда ты говоришь ему про монтирование шары с «server name» — он не знает, никто этого в сеть не вещает.

другой момент, что может тебе и не нужно монтировать каталог при каждой загрузке, а просто закрепить в фм smb-путь до шары, которому можно скормить netbios-имя вида smb://servername/share/ раз так хочется.

Или же банально используй статику или привязку ip к макам на уровне dhcp-сервера, там можно и локальный резолв написать.

Вообще, учитывая что мы обсуждаем файловую шару как сервер — зачем там вообще может быть динамическая адресация?

Anatol: Сообщения: 15; Зарегистрирован: 15 май 2017, 21:08; Благодарил (а): 2 раза; Контактная информация:

mount error could not resolve address

17 май 2017, 19:19

там с организацией сети всё сложно, в сети машины начиная с ХР, заканчивая десяткой. Пользователям(которые и в винде спотыкаются) на минте нужны виндовые шары (их несколько) для складирования туда работы….каждый раз лазить в сеть не вариант, файлов много. Хм, а можно скриптом например монтировать шары при загрузке?

Upd/ Резолв так резолв, посмотрим что получится.

а просто закрепить в фм smb-путь

А фм что это?

di_mok: Сообщения: 5440; Зарегистрирован: 27 авг 2016, 19:06; Решено: 32; Откуда: Арзамас; Благодарил (а): 1569 раз; Поблагодарили: 1263 раза; Контактная информация:

mount error could not resolve address

17 май 2017, 20:29

Anatol писал(а): А фм что это?

Файловый менеджер. Каким ты пользуешься?

Настоящая водка — это не пьянство, а ключ к своей совести, с нее-то и начинается настоящая мудрость. (c)

Anatol: Сообщения: 15; Зарегистрирован: 15 май 2017, 21:08; Благодарил (а): 2 раза; Контактная информация:

mount error could not resolve address

#10

18 май 2017, 07:25

Caja 1.16.1

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

mount error could not resolve address

#11

18 май 2017, 07:39

di_mok, логично, кстати, раз mate )
Anatol, правой кнопкой на папке и должно быть в меню «добавить в закладки» или «добавить на панель».
Или просто папку зажать левой кнопкой и тащить на боковую панель.

Anatol: Сообщения: 15; Зарегистрирован: 15 май 2017, 21:08; Благодарил (а): 2 раза; Контактная информация:

mount error could not resolve address

#12

18 май 2017, 09:26

Там есть примонтировать, но при перезагрузке все примонтированное слетает. На боковую панель не перетаскивается…. А при помещении в закладки не показывает её имя. Вместо него все закладки обозваны smb.

upd/ Вроде нашел как в эту caja впендюрить ссылки на шары. А если шара запаролена, пароли через credentials делать?

upd2/ Оказывается закладку надо вручную переименовать, тогда она сохраняет имя при перезагрузке! Остаться жить на закладках или дальше углубиться в неведомое!?

Dja: Сообщения: 6633; Зарегистрирован: 27 авг 2016, 20:03; Решено: 28; Откуда: Voskresensk; Благодарил (а): 1188 раз; Поблагодарили: 698 раз; Контактная информация:

mount error could not resolve address

#13

27 июл 2017, 08:31

можно еще как вариант попробовать запилить скрипт на подключение с указанием логинов и паролей и прописать в /etc/rc.local выполнять от имени пользователя. В таком случае надо полагать что при окончательной загрузке рабочей сессии — в боковой панели ФМ уже будут все смонтированные места.

upd. что-то попробовал — не получилось

Источник

Печать

Страницы: [1] 2 Все Вниз

Тема: Монтирование расшареного каталога (Прочитано 2806 раз)

0 Пользователей и 1 Гость просматривают эту тему.

freemind

oleg@satellite:~$ sudo mount -t cifs -o username=oleg //B01/сканы/ /mnt/scan mount error: could not resolve address for B01: Unknown errorподскажите, как побороть?
в сети адреса раздаются dhcp, по ip-адресу монтировать нельзя, в hosts я так понимаю тоже нет смысла прописывать

ALiEN175

systemctl status systemd-resolved ping -c4 B01

ASUS P5K-C :: Intel Xeon E5450 @ 3.00GHz :: 8 GB DDR2 :: Radeon R7 260X :: XFCE
ACER 5750G :: Intel Core i5-2450M @ 2.50GHz :: 6 GB DDR3 :: GeForce GT 630M :: XFCE

freemind

oleg@satellite:~$ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendo Drop-In: /lib/systemd/system/systemd-resolved.service.d └─resolvconf.conf Active: inactive (dead) Docs: man:systemd-resolved.service(8)

ALiEN175

sudo systemctl enable systemd-resolved sudo systemctl start systemd-resolved ping -c4 B01

ASUS P5K-C :: Intel Xeon E5450 @ 3.00GHz :: 8 GB DDR2 :: Radeon R7 260X :: XFCE
ACER 5750G :: Intel Core i5-2450M @ 2.50GHz :: 6 GB DDR3 :: GeForce GT 630M :: XFCE

freemind

oleg@satellite:~$ systemctl enable systemd-resolved oleg@satellite:~$ systemctl start systemd-resolved oleg@satellite:~$ ping -c4 B01 ping: unknown host B01 oleg@satellite:~$

oleg@satellite:~$ systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor Drop-In: /lib/systemd/system/systemd-resolved.service.d └─resolvconf.conf Active: active (running) since Сб 2019-09-21 21:00:04 +05; 4min 48s ago Docs: man:systemd-resolved.service(8) Main PID: 16475 (systemd-resolve) Status: "Processing requests..." CGroup: /system.slice/systemd-resolved.service └─16475 /lib/systemd/systemd-resolved


сен 21 21:00:04 satellite systemd[1]: Starting Network Name Resolution...
сен 21 21:00:04 satellite systemd-resolved[16475]: Positive Trust Anchors:
сен 21 21:00:04 satellite systemd-resolved[16475]: . IN DS    19036 8 2 49aac11d
сен 21 21:00:04 satellite systemd-resolved[16475]: Negative trust anchors: 10.in
сен 21 21:00:04 satellite systemd-resolved[16475]: Using system hostname 'satell
сен 21 21:00:04 satellite systemd-resolved[16475]: Switching to system DNS serve
сен 21 21:00:04 satellite systemd[1]: Started Network Name Resolution.
сен 21 21:02:03 satellite systemd[1]: Started Network Name Resolution.
сен 21 21:03:54 satellite systemd[1]: Started Network Name Resolution.
lines 1-20/20 (END)

ALiEN175

ASUS P5K-C :: Intel Xeon E5450 @ 3.00GHz :: 8 GB DDR2 :: Radeon R7 260X :: XFCE
ACER 5750G :: Intel Core i5-2450M @ 2.50GHz :: 6 GB DDR3 :: GeForce GT 630M :: XFCE

freemind

oleg@satellite:~$ smbtree -N WORKGROUP \SATELLITE satellite \SATELLITEKyocera-FS-1125MFP-KPSL Kyocera FS-1125MFP KPSL \SATELLITEGeneric-CUPS-PDF-Printer Generic CUPS-PDF Printer \SATELLITEIPC$ IPC Service (satellite) \SATELLITE1cbase \SATELLITEОбщедоступные \SATELLITEprint$ Printer Drivers \B01 \B01Транспорт \B01Сканы \B01принтер \B01Базы \B01Архивы \B01Users \B01print$ Драйверы принтеров \B01Kyocera FS-1125MFP GX Kyocera FS-1125MFP GX \B01IPC$ Удаленный IPC \B01D$ Стандартный общий ресурс \B01D \B01C$ Стандартный общий ресурс \B01ADMIN$ Удаленный Admin oleg@satellite:~$

victor00000

//B01/

что //google.com/ работает.

freemind

oleg@satellite:~$ ping -c4 smb://B01/ ping: unknown host smb://B01/

oleg@satellite:~$ ping -c4 B01 ping: unknown host B01

Пользователь добавил сообщение 21 Сентября 2019, 21:03:08:

oleg@satellite:~$ ping -c4 ubuntu.ru PING ubuntu.ru (138.201.188.48) 56(84) bytes of data. 64 bytes from ubuntu.ru (138.201.188.48): icmp_seq=1 ttl=48 time=72.5 ms 64 bytes from ubuntu.ru (138.201.188.48): icmp_seq=2 ttl=48 time=72.4 ms 64 bytes from ubuntu.ru (138.201.188.48): icmp_seq=3 ttl=48 time=72.3 ms 64 bytes from ubuntu.ru (138.201.188.48): icmp_seq=4 ttl=48 time=72.3 ms

« Последнее редактирование: 21 Сентября 2019, 21:03:30 от freemind »

victor00000

пишите нормально ИП адрес.
//XXX.XXX.XXX.XXX/

AnrDaemon

freemind, покажите

cat /etc/nsswitch.conf

« Последнее редактирование: 26 Сентября 2019, 00:24:00 от Aleksandru »

Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.

Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…

AnrDaemon

что даёт?

man nsswitch.conf

Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.

Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…

freemind

oleg@satellite:~$ cat /etc/nsswitch.conf # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file.


passwd:         compat
group:          compat
shadow:         compat
gshadow:        files
hosts:          files mdns4_minimal [NOTFOUND=return] dns
networks:       files
protocols:      db files
services:       db files
ethers:         db files
rpc:            db files
netgroup:       nis

AnrDaemon

Либо настройте нормально domain-search, либо пишите имена машин полностью, либо уберите «mdns4_minimal [NOTFOUND=return] » из hosts.

Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.

Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…

freemind

подскажите, что такое domain-search, и как его настроить нормально:)

Имя машины B01, что вы имеете ввиду писать полностью?
//B01/, smb://B01/, //WORKGROUP/B01/, smb://WORKGROUP/B01/ не катят

oleg@satellite:~$ cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 satellite


# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

« Последнее редактирование: 25 Сентября 2019, 11:48:30 от freemind »

Печать

Страницы: [1] 2 Все Вверх

Источник

Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.

bigal: Level 4; Posts: 470; Joined: Mon Aug 03, 2009 3:26 am; Location: Pembrokeshire, South West Wales

[SOLVED] Mounting a share. Could not resolve address

Here we go again.

Two machines, both running 20.1 Cinnamon both fully updated.

I am trying to manually mount a shared folder on the second machine so entered this:

Code: Select all

sudo mount -t cifs //netclient015/015data /home/alan/015data -o uid=1000,gid=1000,credentials=/home/alan/.smbcredentials

I got this error

Code: Select all

mount error: could not resolve address for netclient015: Unknown error

Just to be sure I checked the netbios name and got

Code: Select all

$ nmblookup -A 192.168.0.15
Looking up status of 192.168.0.15 NETCLIENT015    <00> -         B <ACTIVE>

So if the netbios name is correct what else is wrong. I am beginning to think that I am old and stupid. (The local folder does exist although the command doesn’t get that far.)

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Lots of Minty machines but there again I like lamb and I do live in Wales!

altair4: Level 20; Posts: 11021; Joined: Tue Feb 03, 2009 10:27 am

Re: Mounting a share. Could not resolve address

Post

by altair4 » Sun Apr 04, 2021 6:43 am

If you want to be able to address another Linux ( or MacOS or Windows 10 ) machine reliably use it’s mDNS host name ( netclient015.local ) since NetBIOS is effectively disabled today. So your line would read:

Code: Select all

sudo mount -t cifs //netclient015.local/015data /home/alan/015data -o uid=1000,gid=1000,credentials=/home/alan/.smbcredentials

Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

bigal: Level 4; Posts: 470; Joined: Mon Aug 03, 2009 3:26 am; Location: Pembrokeshire, South West Wales

Re: Mounting a share. Could not resolve address

Post

by bigal » Sun Apr 04, 2021 8:56 am

Thank you for that altair4. Following your suggestion worked for me but only so far. I had to amend the share to give guest access. Then it worked. That done I found that any new folders or files on the share were owned by nobody in the nobody group. I tried altering the username and password in the .smbcredentials files to that on the remote machine thinking that might be the source of the problem but obviously it is not. It was a bit of a long shot. Can you help again please?

Once I get the manual mount sorted my plan is to add it to my fstab file but one thing at a a time.

Lots of Minty machines but there again I like lamb and I do live in Wales!

altair4: Level 20; Posts: 11021; Joined: Tue Feb 03, 2009 10:27 am

Re: Mounting a share. Could not resolve address

Post

by altair4 » Sun Apr 04, 2021 9:07 am

It would be best if you were to post the output of the following commands from the server:

That way any response would be tailored to your setup.

Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

bigal: Level 4; Posts: 470; Joined: Mon Aug 03, 2009 3:26 am; Location: Pembrokeshire, South West Wales

Re: Mounting a share. Could not resolve address

Post

by bigal » Sun Apr 04, 2021 9:20 am

Code: Select all

$ testparm -s
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
	client max protocol = NT1
	log file = /var/log/samba/log.%m
	logging = file
	map to guest = Bad User
	max log size = 1000
	obey pam restrictions = Yes
	pam password change = Yes
	panic action = /usr/share/samba/panic-action %d
	passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
	passwd program = /usr/bin/passwd %u
	server role = standalone server
	server string = %h server (Samba, Ubuntu)
	unix password sync = Yes
	usershare allow guests = Yes
	idmap config * : backend = tdb
	force user = alan


[printers]
	browseable = No
	comment = All Printers
	create mask = 0700
	path = /var/spool/samba
	printable = Yes


[print$]
	comment = Printer Drivers
	path = /var/lib/samba/printers

No output whatsoever.

Lots of Minty machines but there again I like lamb and I do live in Wales!

bigal: Level 4; Posts: 470; Joined: Mon Aug 03, 2009 3:26 am; Location: Pembrokeshire, South West Wales

Re: Mounting a share. Could not resolve address

Post

by bigal » Sun Apr 04, 2021 10:17 am

That is the output from the client.
Sorry I should have said. Here is the output from the ‘server’ machine.

Code: Select all

$ testparm -s
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

# Global parameters
[global]
	log file = /var/log/samba/log.%m
	logging = file
	map to guest = Bad User
	max log size = 1000
	obey pam restrictions = Yes
	pam password change = Yes
	panic action = /usr/share/samba/panic-action %d
	passwd chat = *Entersnews*spassword:* %nn *Retypesnews*spassword:* %nn *passwordsupdatedssuccessfully* .
	passwd program = /usr/bin/passwd %u
	server role = standalone server
	server string = %h server (Samba, Ubuntu)
	unix password sync = Yes
	usershare allow guests = Yes
	idmap config * : backend = tdb
	force user = alan


[printers]
	browseable = No
	comment = All Printers
	create mask = 0700
	path = /var/spool/samba
	printable = Yes


[print$]
	comment = Printer Drivers
	path = /var/lib/samba/printers

Code: Select all

$ net usershare info --long
[015data]
path=/home/alan/015data
comment=From 2021-04-03
usershare_acl=Everyone:F,
guest_ok=n

Lots of Minty machines but there again I like lamb and I do live in Wales!

altair4: Level 20; Posts: 11021; Joined: Tue Feb 03, 2009 10:27 am

Re: Mounting a share. Could not resolve address

Post

by altair4 » Sun Apr 04, 2021 10:25 am

It looks like your server is set up correctly.

You included the force user = alan in your [global] section so all new files added would be saved with owner = «alan».

I see no issue with this.

Your share is designed for credentialed user so you would have to set a samba password for that user even if the remote user was «alan» — so on the server:

Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

bigal: Level 4; Posts: 470; Joined: Mon Aug 03, 2009 3:26 am; Location: Pembrokeshire, South West Wales

Re: Mounting a share. Could not resolve address

Post

by bigal » Sun Apr 04, 2021 11:31 am

I set the smbpasswd on the server machine to be the same as its logon password. That didn’t work so I tried using the login password for the client machine. That didn’t work either. Both times I got

$ sudo mount -t cifs //netclient015.local/015data /home/alan/015data -o uid=1000,gid=1000,credentials=/home/alan/.smbcredentials
mount error(13): Permission denied

I’m sorry but I am way out of my depth here.

Lots of Minty machines but there again I like lamb and I do live in Wales!

altair4: Level 20; Posts: 11021; Joined: Tue Feb 03, 2009 10:27 am

Re: Mounting a share. Could not resolve address

Post

by altair4 » Sun Apr 04, 2021 11:36 am

Go back to the server. Change your share definition to allow guest access with write access.

On the client access that share this way:

Code: Select all

sudo mount -t cifs //netclient015.local/015data /home/alan/015data -o guest,uid=1000,gid=1000

Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

bigal: Level 4; Posts: 470; Joined: Mon Aug 03, 2009 3:26 am; Location: Pembrokeshire, South West Wales

Re: Mounting a share. Could not resolve address

Post

by bigal » Sun Apr 04, 2021 11:52 am

Wahoo!!!!! That worked. I have read and write access to the share. Do I leave it at that or is there some further change before I try to set it up in fstab?

Lots of Minty machines but there again I like lamb and I do live in Wales!

altair4: Level 20; Posts: 11021; Joined: Tue Feb 03, 2009 10:27 am

Re: Mounting a share. Could not resolve address

Post

by altair4 » Sun Apr 04, 2021 11:58 am

I would recommend the following approach to fstab. Set it up this way:

[1] Unmount the share first:

[2] Then in fstab the line I’m suggesting would look like this:

Code: Select all

//netclient015.local/015data /home/alan/015data cifs guest,uid=1000,gid=1000,noauto,user 0 0

Save fstab.

When you open Nemo you should see the 015data folder on the left side panel. When selected it will go to fstab to find out how to mount it then display the shares contents — gods willing.

Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

bigal: Level 4; Posts: 470; Joined: Mon Aug 03, 2009 3:26 am; Location: Pembrokeshire, South West Wales

Re: Mounting a share. Could not resolve address

Post

by bigal » Sun Apr 04, 2021 12:21 pm

Altair4, I had never realised before but now I know.

Linux Mint keeps you fit.

The two machines we have been talking about are in separate buildings around 80m apart. I have had plenty of my daily exercise rushing between the two far more times than I care to count. I’ll need a new boot on the end of my walking stick next.

It was all worth it though. IT WORKS. Thank you so much for all the help and for sticking with me. You have no idea just how grateful I am.

I am marking this post as solved.

Lots of Minty machines but there again I like lamb and I do live in Wales!

bigal: Level 4; Posts: 470; Joined: Mon Aug 03, 2009 3:26 am; Location: Pembrokeshire, South West Wales

Re: [SOLVED] Mounting a share. Could not resolve address

Post

by bigal » Tue Apr 27, 2021 2:16 pm

Although my shared folder is set up exactly as altair4 advised and is accessible on the ‘client’ machine exactly as he thought it would I am puzzled by a couple of things.

While the share does indeed shew up in the left side panel of Nemo, if I open the ‘Network’ folder it does not. What I still see is

NETCLIENT015 (File Sharing) — unknown type — unknown modification date

I do not understand why.

There is an additional, supplementary, question and that is can I set a fstab entry in the ‘client’ machine to open the link upon startup?

Lots of Minty machines but there again I like lamb and I do live in Wales!

altair4: Level 20; Posts: 11021; Joined: Tue Feb 03, 2009 10:27 am

Re: [SOLVED] Mounting a share. Could not resolve address

Post

by altair4 » Tue Apr 27, 2021 5:29 pm

What do you mean by «open the link upon startup»?

You mean you want the share to mount and open nemo to that mount point when you login?

Menu > System Settings > Startup Applications > + ( to Add )

Give it a name

Then for the command enter:

Code: Select all

bash -c 'mount /home/alan/015data;nemo /home/alan/015data'

If it’s currently mounted unmount it then logoff and login again. Your partition should mount and open nemo to the mount point.

You may have to play with the «startup delay» setting depending on how obstinate the networking stack is on Mint.

Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

Источник

Ошибка при монтировании по сети

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

mount error could not resolve address

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> freemind

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useron.png" alt="Онлайн" /> ALiEN175

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> freemind

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useron.png" alt="Онлайн" /> ALiEN175

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> freemind

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useron.png" alt="Онлайн" /> ALiEN175

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> freemind

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> victor00000

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> freemind

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> victor00000

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> AnrDaemon

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> AnrDaemon

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> freemind

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> AnrDaemon

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://forum.ubuntu.ru/Themes/ubuntu-portal/images/png/useroff.png" alt="Оффлайн" /> freemind

[SOLVED] Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: Mounting a share. Could not resolve address

Re: [SOLVED] Mounting a share. Could not resolve address

Re: [SOLVED] Mounting a share. Could not resolve address

freemind

ALiEN175

freemind

ALiEN175

freemind

ALiEN175

freemind

victor00000

freemind

victor00000

AnrDaemon

AnrDaemon

freemind

AnrDaemon

freemind