mtense

Great. I figured someone had solved this problem already. I will look into it. Thanks!

How about adding something like make sure all your "extra" packages are compatible with slackware version. Bit me hard. The push button upgrades are great, but can sure bite you...

My shares are back after finding this post. I was installing glibc-2.17-x86_64-7.txz so that I could build perl modules. With installpkg for commented out glibc-2.17-x86_64-7.txz, shares are back! I assume I need to upgrade.

Argh. Lost many hours until I came across this post. Thanks a million puweyxil. I was installing glibc-2.17-x86_64-7.txz so that I could build perl modules. I assume I need to upgrade. Anyway, will installpkg commented out, shares are back!

So, I tried watching traffic on 445, 137, and 139 to make sure samba is working. When I restart samba (/etc/rc.d/rc.samba restart), I see it broadcasting. See first image. Sorry I can't figure out to export summary view in wireshark. I am a noob. My PC: 192.168.123.65 (electra) Unraid: 192.168.123.64 (nas) The workgroup is PETEDOG. When I try to access unraid from windows file explorer by \\192.168.123.64, I appear to get a bunch of resets (RST?). Can anyone help me decipher these? Thanks, Aaron

Unfortunately, no. Using the IP address doesn't work.

I am running 6.3.5. I have been primarily using plex on the unraid server and somewhere along the way I lost access to shares on the network. I might have lost the shares with upgrading from 5 to 6.3, but it seems unlikely that I didn't check all was working then. It has been a while, so I really don't trust my memory. I apologize for the lack of info, but am hoping I can get some help moving forward. I can't see the server (doesn't show up in network) with Windows 10, Mac or Android. I have checked the Workgroup settings are consistent (PETEDOG). I also installed the Master Browser plugin and checked that unraid is the master. The server only has one nic, so no issues there. I have tried the SMB parameters: ntlm auth = yes max protocol = SMB2_02 I have also tried registry entries: \SYSTEM\CurrentControlSet\Services\Browser\Parameters\MaintainServerList=No SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\AllowInsecureGuestAuth=1 I tried booting in safe mode and have attached diagnostics. Thanks in advance for any help you can provide. Cheers, Aaron nas-safemode-diagnostics-20170903-1030.zip nas-safemode-syslog-20170903-1031.zip

I have some perl scripts running on my unraid box that need a couple perl modules. Took some googling and testing to get it figured out (a couple years ago). I figured I would post what works for me in hopes that it will help someone else. Here are the relevant parts of my go script. installpkg /boot/packages/gcc-4.2.4-i486-1.tgz installpkg /boot/packages/glibc-2.7-i486-17.tgz installpkg /boot/packages/binutils-2.18.50.0.9-i486-1.tgz installpkg /boot/packages/make-3.81-i486-1.tgz installpkg /boot/packages/kernel-headers-2.6.27.7_smp-x86-1.tgz installpkg /boot/packages/cxxlibs-6.0.9-i486-1.tgz installpkg /boot/custom/perl/perl-5.10.0-i486-1.tgz PERL_MM_USE_DEFAULT=1 cpan App::cpanminus PERL_MM_USE_DEFAULT=1 cpanm LWP::Simple mkdir /tmp/src cd /tmp/src cp /boot/packages/curl-7.25.0.tar.gz . tar xzf curl-7.25.0.tar.gz cd curl-7.25.0 ./configure make make install cp /usr/local/lib/* /usr/lib

Doh, when I configured several weeks ago I chose not the export the flash drive b/c I couldn't think why I would need to at the time. Completely forgot it could be exported. That was the bit I was missing. Thanks for all the help!!!

So, this prompts a follow up question. How to most users edit files like /boot/config/go remotely? My unraid server is sitting in a closet, so it seems the options are - copy file to location on shared disks, edit, copy it back - sneaker net the usb to my desktop, edit, sneaker net back - use vi Am I missing some easier way? I just get by in vi, so not love lost ;-) Thx, A

Thanks for the suggestions. I found a solution (below), but I tried these to see if they would help. The TERM was already set to ansi, so the first one didn't help. Setting the TERM to xterm was even worse. After I found out that vi was a link to nvi vi -> nvi* I decided to try vim instead. It works just dandy for TERM=ansi. Strange that this isn't a common problem given my relatively vanilla configuration. Regards, Aaron

So, I got sshd running and tried logging in with that. When I try to vi via ssh, I get vi: cygwin: unknown terminal type What a pain. Can someone help me understand what up? Thanks, Aaron

When I telnet from XP to the unraid server, vi behaves erratically. Initially the file does not display correctly, arrow keys produce control chars, a simple 'x' erases the whole screen. As an example, my working go file looks like this after a 'vi go' from the command prompt. [0;10;7mUsage: [[ installpkg /boot/packages/socat-1.7.0.0-i486-2bj.tgzk12.1.tgz installpkg /boot/packages/unraid_notify-2.54-noarch-unRAID.tgz rontab -l >/tmp/crontab echo "0 2 * * * /boot/daily_backups.sh 1>/dev/null 2>&1" >>/tmp/crontab cp /tmp/crontab /var/spool/cron/crontabs/root- crontab /tmp/crontab There are missing lines, missing letters and garbage at the top. I tried changing terminal type to vt100, but that didn't work. I have ensured there are not PC newlines. Any suggestions on what is going on? Best, Aaron