server not seen by clients after upgrade

Have you set samba passwords for your users?

all machines are connected to the server with my credentials which is sysadmin on the server. All shares are verified with my credentials. All Win10 machines are running "workgroup" with work network settings (not homegroup). Everything went south when the upgrade went through. It connected fine prior to the upgrade. Even my PLEX media server cannot be reached. That is another issue but may be connected. Ifconfig show proper lan IP assignments and default localmachine of 127.0.0.0 with loopback. Originally immediately after the upgrade the file systems were read only and I was dumped on the command line. I managed to sort that out but I am obviously limited in my linux experience. I have my GUI back and mounted all RAID shares and verified they were accessible locally. All shares on the server seem to be intact and not changed. I suspect something was reset to defaults when the upgrade was accomplished. Also as the upgrade was taking place there were several "program errors" that requested I send the info back which I agreed to. I also note that instead of the single "fail" in the list that was in the boot list in the old system that was just a repeat of a duplicate command I see over a dozen fails as the system is booting. This server has been in operation for two years. After the upgrade it is a standalone desktop.

I can't connect to the server to verify credentials. Connection refused at the server. When running the troubleshooter from Win10 network control the server cannot be found although I can ping it.

"The remote device or resource won't accept the connection" when trying to connect using IP address and share. the server is flat out rejecting any connections.

message from Linux when trying to share again suggests that smbd is not running.
Keith<servername>~$ smbd
[date,time ,0] ../lib/util/debug.c:597 (reopens_logs_internal)
unable to open new log file '/var/log/samba/log.smbd :Permission Denied
[date,time ,0] ../source3/lib/dumpcore.c:249 (dump_core_setup)
unable to setup corepath for smbd :Operation not permitted
[date,time, 0] ../lib/util/debug.c:597 (reopens_log_internal)
unable to open new log file '/var/log/samba/log.smbd :Permission Denied
[date,time, 0] ../source3/smbd/server.c:1189 (main)
smbd version 4.1.13-ubuntu started.
copyright samba team
Keith<servername>~$
It says smbd is started so this to me says it is a permission issue and somehow I no longer have the correct permissions to operate these shares after the upgrade. So a hint from a seasoned veteran would be greatly appreciated. If further information is needed please inform me of what and how to get it. But I could be way off base and it is something else.

In smb.conf there is only the message about the local l network address of 127.0.0.0/8 eth0. That is the wrong address for the ethernet connection. This should be 192.168.0.2/? eth0.? Should I add the address to the statement or replace the statement with the actual values for eth0?

Every damn thing they did in the upgrade is read only. I cannot edit the smb.conf file. I can't save the edit. I am a novice and don't use Linux much at all except for the server. It has all my backups and files for the network. It is just a file server but it is now a POS. Thanks UBUNTU.

Didn't you do some tests before trying to upgrade your important server system?

If you want to modify system settings (like the smb.conf file), you need administrative privileges.
To do that on Ubuntu you usually use the sudo command prefix.

In you case this would most probably mean to issue the command

sudo gedit /etc/samba/smb.conf
or
sudo nano /etc/samba/smb.conf

I am not used to toy operating systems that have no support. NO this did not solve the issue. Your toy system has failed miserably.
Testing what? It worked fine. This POS is NOT supported. I can get on the horn and talk to a tech to solve the problems on the machines with good operating systems. You know the kind you can talk to a dedicated technician instead of a motley collection of holier than thou hobbyist. Those are the ones you don't have to use a a hobby. I am not a linux progammer one of you jerks talked me into using it instead of my choice of a supported operating system.
Problem solved. Removed that piece of shit and replaced the drive which I loaded with a good operating sytem with support as the raids were all NTFS and I can now see and access them So take your toy operating systems and shove them up your ass.

I am not used to toy operating systems that have no support. NO this did not solve the issue. Your toy system has failed miserably.
Testing what? It worked fine. This POS is NOT supported. I can get on the horn and talk to a tech to solve the problems on the machines with good operating systems. You know the kind you can talk to a dedicated technician instead of a motley collection of holier than thou hobbyist. Those are the ones you don't have to use a a hobby. I am not a linux progammer one of you jerks talked me into using it instead of my choice of a supported operating system.
Problem solved. Removed that piece of shit and replaced the drive which I loaded with a good operating sytem with support as the raids were all NTFS and I can now see and access them So take your toy operating systems and shove them up your ass.

I am not used to toy operating systems that have no support. NO this did not solve the issue. Your toy system has failed miserably.
Testing what? It worked fine. This POS is NOT supported. I can get on the horn and talk to a tech to solve the problems on the machines with good operating systems. You know the kind you can talk to a dedicated technician instead of a motley collection of holier than thou hobbyist. Those are the ones you don't have to use a a hobby. I am not a linux progammer one of you jerks talked me into using it instead of my choice of a supported operating system.
Problem solved. Removed that piece of shit and replaced the drive which I loaded with a good operating sytem with support as the raids were all NTFS and I can now see and access them So take your toy operating systems and shove them up your ass.

Constructive.... Really classy too.

Sad

Please mark as solved if the issue is as such

Can one of the administrators please ban "Keith Morgavi (kmorgavi)" for absolute inappropriate language in his comments, clearly failing to abide the Ubuntu code of conduct.

You don't have to ban me you holier than thou piece of shit worthless toy promoter. I took the advice of one of you assholes and when what YOU did(Ubuntu) fucked up everything and when I ask for help you first have to attack me with snide remarks better suited to one of you jerks that claim they "support" this piece of shit than to someone who trusted one of you and got hammered. FUCK YOU and LINUX and Ubuntu