Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Tech N Gamer

Member
  • Content Count

    474
  • Joined

  • Last visited

Awards


This user doesn't have any awards

About Tech N Gamer

  • Title
    Member
  • Birthday 1997-09-18

Contact Methods

  • Steam
    http://steamcommunity.com/id/Tech_N_Games

Profile Information

  • Gender
    Male
  • Location
    Earth
  • Interests
    Computer Science, Science in general, Technology

System

Recent Profile Visitors

2,383 profile views
  1. No. The router is too far away and off of its jacks are taken up.
  2. I have found a workaround, and I think I know what the issue is. So, at startup, there is no internet connection therefor Samba is unable to bind to an ip/port. The workaround is to disable smbd.service and create smbd.timer. In the timer file located at /usr/lib/systemd/system/ I'd put in: [Unit] Description=Runs smbd 1 minutes after restart. [Timer] OnBootSec=1min [Install] WantedBy=timers.target And now it works fine aside from having to wait a minute till it starts it.
  3. In the first message, after the reboot, this message appears: Apr 22 14:56:26 Data_Laptop smbd[431]: [2018/04/22 14:56:26.377492, 0] ../source3/lib/util_sock.c:396(open_socket_in) Apr 22 14:56:26 Data_Laptop smbd[431]: bind failed on port 445 socket_addr = 2602:306:bd16:2d20:a2c:b33b:67f9:652c. Apr 22 14:56:26 Data_Laptop smbd[431]: Error = Cannot assign requested address Apr 22 14:56:26 Data_Laptop smbd[431]: [2018/04/22 14:56:26.377722, 0] ../source3/smbd/server.c:1093(smbd_open_one_soc> Apr 22 14:56:26 Data_Laptop smbd[431]: smbd_open_one_socket: open_socket_in: Cannot assign requested address Apr 22 14:56:26 Data_Laptop smbd[431]: [2018/04/22 14:56:26.377761, 0] ../source3/lib/util_sock.c:396(open_socket_in) Apr 22 14:56:26 Data_Laptop smbd[431]: bind failed on port 139 socket_addr = 2602:306:bd16:2d20:a2c:b33b:67f9:652c. Apr 22 14:56:26 Data_Laptop smbd[431]: Error = Cannot assign requested address Apr 22 14:56:26 Data_Laptop smbd[431]: [2018/04/22 14:56:26.377808, 0] ../source3/smbd/server.c:1093(smbd_open_one_soc> Apr 22 14:56:26 Data_Laptop smbd[431]: smbd_open_one_socket: open_socket_in: Cannot assign requested address After I restart the service, it's gone.
  4. I created the path to the log file, restarted the system to test if it worked, and it didn't change the outcome. SMB Share's is inaccessible until I restart the service.
  5. This is the output of that. ● smbd.service - Samba SMB/CIFS server Loaded: loaded (/usr/lib/systemd/system/smbd.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2018-04-22 13:58:22 CDT; 47s ago Process: 388 ExecStart=/usr/bin/smbd -D (code=exited, status=0/SUCCESS) Main PID: 414 (smbd) Tasks: 4 (limit: 4915) Memory: 30.0M CGroup: /system.slice/smbd.service ├─414 /usr/bin/smbd -D ├─416 /usr/bin/smbd -D ├─417 /usr/bin/smbd -D └─418 /usr/bin/smbd -D Apr 22 13:58:22 Data_Laptop smbd[388]: [2018/04/22 13:58:22.660768, 0] ../lib/util/debug.c:1053(reopen_logs_internal) Apr 22 13:58:22 Data_Laptop smbd[388]: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory Apr 22 13:58:23 Data_Laptop smbd[414]: [2018/04/22 13:58:23.269761, 0] ../lib/util/debug.c:1053(reopen_logs_internal) Apr 22 13:58:23 Data_Laptop smbd[414]: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory Apr 22 13:58:23 Data_Laptop smbd[414]: [2018/04/22 13:58:23.269993, 0] ../lib/util/debug.c:1053(reopen_logs_internal) Apr 22 13:58:23 Data_Laptop smbd[414]: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory Apr 22 13:58:23 Data_Laptop smbd[414]: [2018/04/22 13:58:23.269713, 0] ../lib/util/become_daemon.c:124(daemon_ready) Apr 22 13:58:23 Data_Laptop smbd[414]: STATUS=daemon 'smbd' finished starting up and ready to serve connections Apr 22 13:58:23 Data_Laptop smbd[418]: [2018/04/22 13:58:23.312547, 0] ../lib/util/debug.c:1053(reopen_logs_internal) Apr 22 13:58:23 Data_Laptop smbd[418]: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory By the way, this SMB Server is just an old laptop that I repurposed into an SMB server.
  6. Yes, it is accessible after I do that. It becomes inaccessible when Arch restarts or starts up after shutdown. The service is enabled. I have a script that makes sure the system is up to date and restarts once it is to force anything running to use the newer version.
  7. That didn't work, still, have to SSH or go to it and type sudo systemctl restart smbd.
  8. First off, I have no idea where to put this, I'm putting it here since it's a Linux issue. Secondly, no matter which OS I'm using, rather it is Arch or Windows, I cannot access my SMB shares. I have to SSH into the device (or walk over to it and log in) and type: sudo systemctl restart smbd It's annoying since I have a script that will run pacman and update the system and once updated, it will restart it. Problem is, Samba won't load/broadcast any shares listed in the config. Please help.
  9. Apparently, it was missing font and/or the font cache wasn't able their.
  10. I was able to fix it by doing the following on tty2: mkdir /usr/share/fonts/WindowsFonts cp -vR /windows/Windows/Fonts/* /usr/share/fonts/WindowsFonts chmod -vR 755 /usr/share/fonts/WindowsFonts fc-cache -f
  11. Yes, and now it's just a bunch of symbols after I opened Visual Studio Code. Both VS Code and the Deepin Terminal are just fucked up. I've tried rebooting and reinstalling everything. EDIT: BTW, I know it's not VS Code since both worked in the past and never did this.
  12. Can someone help me, I have no idea why the text is all crunched together, in most applications the text is fine, but in others, it's crammed together. I also have Steam installed.
  13. From what I can tell, the major distro's are both UEFI and BIOS compatible, along with what bootloader you're using.
×