Accessing Network issues ( AGAIN )

FatRakoon · 5 Jul 2023 at 23:20

Ok, this has happened before, but the previous solutions are not helping.

Well, they sort of semi are.

Many PCs, all 64 Bit now, some Windows 10 and some Linux ( usually Mint Cinnamon, But Ubuntu Remix )

Now, the main PC and the Server are both running the same version of Windows 10, but the Main PC is PRO and the Server is Enterprise.
The versions are 22H2 / 19045.3086

The Server I can access with some level of success, but the Main PC, not so much.

At best, I can see it, but I cannot access it, and now I cannot see it, and if I manually enter smb://kabylake/d/ then I do have access to its files on D: - I can of course do this for all its drives. but I cannot just have kabylake? I can with the Sever.

All I cant to do, is to be able to just click on the network, see my PCs and the LAN Devices ( Those are also seen but I cannot access ) and open them and access the files, but I am simply unable to.

I have of course tried to edit the smb.conf file and I have tried min and max protocols with various settings, with client and server and neither and all using SMB and NT options, anmd I get various levels of some access but then seem to lose other?

Its really doing my pip in I have to be honest, and I really dont know what I am doing, other than client max protocol = NT1 used to work a treat, but it simply does not anymore?

Why does Enterprise work better then Pro ? There is clearly something there surely?

Also, as I mentioned earlier, I am able to see my LAN Drives. I have 2 DLINK and 2 NETGEARS and they show up, But I am unable to access them.
Right now, the DLINKS simply fail, the Netgears give me the box saying that they are accessing them, then I get a blank window.
Again, this never used to happen before.

Anyone know what the hell I need to try? Please note, that I am a douche and have mental issues.

FatRakoon · 10 Jul 2023 at 01:25

Heck, I am aware you replied, but I have simply NOT had the time to check the PC recently.
I will do though, thanks.

FatRakoon · 10 Jul 2023 at 17:51

Ok, lets see if this will help in anyway.

I am going to double click on things and tell you what happens ok?

Right now, I am on the MINT 21.1 - Cinnamon setup

Double Click on NETWORK Icon

Dialog show up - Opening Network..

Page opens up showing all PCs including DLINK and NETGEAR Shares, even the Blackberry Classic!

So, I double click SERVER...
Authentication Required ( Linuxs keyring thingy? )
Dialog - opening Network...
Authentication Required ( Username, Domain, Password for the Windows PC )
Enter the User / Password and I get in... GREAT!

So, I double Click on the MASTER...
Unable To Mount location
Failed to retrieve share list from server: Network location dropped on reset

Now, if I go back to the Server and into, lets say Drive D:
I then show the address on the Nemo address line and I see :-

smb://server/d/

Ok, cool, now, if I change "server" to "master", I get access to the Drive D: on the Master

smb://master/d/

Now, if I shorten this and type in

smb://server

I get access to all the drives, that are in the server, including a couple of others such as ADMIN$ and the drives, plus the drives with a dollar $ sign.

However, if I try this with the master, I dont get any of that and instead, I get another failure?

Could not display "smb://master/
Failed to retrieve share list from server: Network location dropped on reset
Please select another viewer and try again.

So, I can access the files, but only if I mannually enter the direct location to each partition/Drive

If I was to try to open the NETGEAR LAN Drives...

It currently opens up Nemo with it displaying nothing?

It shows the Netgear Icons in the list in 2 ways:-
RN104-1
RN104-1(File Sharing)
RN104-2
RN104-2(File Sharing)
Both the Netgears do this

The DLinks both just show as
DLINK-A(File Sharing)
DLINK-B(File Sharing)

They both open up onto the 2 Volumes, but when I try clicking on either of these on either of the DLINKS, I get:-

Unable To Mount location
Failed to mount Windows Share: Software Caused connection abort.

So, what I am limited to, is accessing the Server, is fine and seems to work as it should.
Accessing the Master can ONLY be done by directly entering the address Manually for each partition.
Accessing either the DLinks or the Netgears is not happening?

Now, in the main windows when I Double-Click on the NETWORK Icon, when it displays all the network devices, it also shows a windows network Icon.
Opening this up, then shows me a WORKGROUP Icon. As I have kept things to the defaults in all the PCs this is obviously the only one workgroup that I have.

Double clicking on that shows me the devices again, but only one DLINK and one NETGEAR.

Trying to access anything via this icon gives me the same results as before.

I am not sure if me giving you my smb.conf file would help, but, right now, the ONLY changes to the default file, is that I have added these lines under [global]

workgroup = WORKGROUP
client min protocol = SMB2
client max protocol = SMB3
server min protocol = SMB2
server max protocol = SMB3
min protocol = SMB2
max protocol = SMB3

I have, of course been experimenting with various options and there does not seem to be any difference in how they work. I have also tried NT1 as I am sure that this was what was needed since Mint v18.3 but I dunno?

I have tried to make this as basic and simple as I can, however, I have a feeling that I have failed and its as clear as mud.

What I am going to do shortly, is install an older version of Linux, and see what happens there, just for the giggles.

But if you understand WTF is going on, then please advise me.

Thanks.

FatRakoon · 12 Jul 2023 at 14:01

El Pew said:
I gave you some advice in my previous post - have you tried any of that?

Sorry yes, I have, what I understand of it anyway.

You mentioned.
1. SMB relies to an extent on DNS. Make sure your client machines can properly resolve the IP of both of your Windows server based machines. Or alternatively avoid DNS altogether by using IPs to connect, e.g. smb://192.168.1.10/d (or whatever the IP is).
2. Firewalls - make sure the required SMB ports (139 and 445) are open on both Windows machines for the client machines.
3. Make sure the SMB service is running properly on both Windows machines.
4. You don't mention if you are using an Active Directory domain but if you are make sure all machines are on the domain correctly and that you have valid domain credentials to use.
5. Speaking of authentication, it might be that you cannot connect because you have invalid credentials. These might be cached somewhere on your client, if so make sure to clear the cache. Not sure how this works on Mint or Ubuntu but Google "clear SMB credential cache".

1 - SMB/DNS
I see and have full access to the Server.
I see but DONT have full access to the Master, however, if I pass the root of master if you like, and go directly to its partitions, 'I can do it.
This is also the same if I go directly to their IP

2 - Firewall
Both 139 and 445 are open

3 - SMB on both Windows machines.
Erm, how do I do that?

4 - Active Domain.
No, not using that.

5- Authentication.
Perhaps, but this is ona fresh install too! - I have however cleared the Credential cache on the Windows PCs but not sure on mint, so yes I will have a look, but as I said, this is on a fresh install and so the cache would not need to be refreshed surely?

ok, so, I may seem like I am not listening to you, I promise you I am, but I dont have much time and then I am rushed, plus I have mental issues and so I only have an hour or two in between medication and brain fart that I can actually concentrate on anything, Im also trying to sort out my main Linux PC as thats just decided to have a funky HD that is giving me a headache, so I am also trying to sort that out.