Hi, to clarify I have never used WiFi on my CosmosEx. I've no idea why these wifi options are available in the Network Settings of my CosmosEx. I have never enabled wifi in any way on my cosmosex as far as I'm aware. My cosmosex is connected to my home network with a standard ethernet cable. If anyone knows of a way of completely disabling these unwanted wifi settings to stop them from appearing in the Network Settings screen then please let me know. I suspect these unpopulated wifi settings are not the cause of my issues here though.
So, what's the difference between my NAS and my Windows10 PC... which means I can use my CosmosEx to access a shared drive on my Windows10 PC but not on my NAS?
Thanks.
CosmosEx 3.0 issues - can't get it to work [SOLVED]
Moderators: Jookie, Moderator Team
-
- Atariator
- Posts: 28
- Joined: Wed Dec 16, 2015 4:15 pm
Re: CosmosEx 3.0 issues - can't get it to work [SOLVED]
Not sure its difficult to look at your network from here.
What I sometimes do with networks is make a drawing and write down ip's and draw connections.
It looks like something is disconnected or blocking.
- change netwok cable
- Security in your router allows only selected trusted devices?
- NAS security/firewall blocking look at logs
What I sometimes do with networks is make a drawing and write down ip's and draw connections.
It looks like something is disconnected or blocking.
- change netwok cable
- Security in your router allows only selected trusted devices?
- NAS security/firewall blocking look at logs
Falcon030, TT030, Mega ST, 1040STfm, 800XL, Lynx, Jaguar, Portfolio
-
- Atariator
- Posts: 28
- Joined: Wed Dec 16, 2015 4:15 pm
Re: CosmosEx 3.0 issues - can't get it to work [SOLVED]
Thanks for the pointers folks...
I'm currently wondering whether the reason my CosmosEx is struggling to map a shared drive to my NAS (via CIFS) is because the only type of CIFS supported by my NAS is SMB1.0. My NAS is a D-Link DNS-320L and is now out of support so it will never receive support for SMB2 or later.
As mentioned previously I can successfully map a network drive from my Windows10 PC to the same cifs share on my NAS. However the only way I was able to do this was to enabled the 'SMB 1.0/CIFS Client' in 'file sharing support' on my Windows 10 PC. Prior to enabling the SMB1.0 client on my Windows10 PC I was unable to map a network drive from my Windows10 PC to my NAS.
I understand that SMB1.0 is generally regarded as a security vulnerability these days. In April 2018 Microsoft disabled support for SMB1.0 by default in their Windows operating systems. Therefore I'm thinking a similar thing may have happened to Linux around the same time...?
Does anyone know any of the following...
- Is the 'SMB 1.0/CIFS Client' enabled or disabled by default in the Linux Raspbian distro (that's currently on my CosmosEx)...?
- What versions of SMB are supported by Raspbian...?
- How do I ensure that SMB1.0 is enabled in Raspbian on my CosmosEx...? (yes I understand this is probably not advisable for security reasons)
If there's no way of enabling support for SMB1.0 on my CosmosEx then I guess the only way forward is to buy myself a more modern NAS that supports a later version of SMB.
Your thoughts?
Thank you all.
I'm currently wondering whether the reason my CosmosEx is struggling to map a shared drive to my NAS (via CIFS) is because the only type of CIFS supported by my NAS is SMB1.0. My NAS is a D-Link DNS-320L and is now out of support so it will never receive support for SMB2 or later.
As mentioned previously I can successfully map a network drive from my Windows10 PC to the same cifs share on my NAS. However the only way I was able to do this was to enabled the 'SMB 1.0/CIFS Client' in 'file sharing support' on my Windows 10 PC. Prior to enabling the SMB1.0 client on my Windows10 PC I was unable to map a network drive from my Windows10 PC to my NAS.
I understand that SMB1.0 is generally regarded as a security vulnerability these days. In April 2018 Microsoft disabled support for SMB1.0 by default in their Windows operating systems. Therefore I'm thinking a similar thing may have happened to Linux around the same time...?
Does anyone know any of the following...
- Is the 'SMB 1.0/CIFS Client' enabled or disabled by default in the Linux Raspbian distro (that's currently on my CosmosEx)...?
- What versions of SMB are supported by Raspbian...?
- How do I ensure that SMB1.0 is enabled in Raspbian on my CosmosEx...? (yes I understand this is probably not advisable for security reasons)
If there's no way of enabling support for SMB1.0 on my CosmosEx then I guess the only way forward is to buy myself a more modern NAS that supports a later version of SMB.
Your thoughts?
Thank you all.
-
- Atariator
- Posts: 28
- Joined: Wed Dec 16, 2015 4:15 pm
Re: CosmosEx 3.0 issues - can't get it to work [SOLVED]
Hi folks, I have just put the Yocto distro back on my CosmosEx and the 'Shared Drive' feature mapped to my NAS now works fine Ideally however I would like to be using the latest Raspbian-Stretch distro on my CosmosEx.
As mentioned above, the latest version of 'SMB' (cifs) network file sharing protocol supported by my NAS is SMB1.0. I know that the SMB1.0 client is disabled by default in Windows10 since 2018. I know very little about Linux but I can only assume that the SMB1.0 client is also disabled by default in the latest Linux distros like Raspbian-Stretch.
So the million dollar question here is... how do I enable support for the SMB1.0 client in the Raspbian-Stretch distro of Linux...?
Or can anyone think of any other differences between Yocto and Raspbian-Stretch that might be causing the 'Shared Drive' feature of my CEx to not work?
If I cannot get all of the CosmosEx features working (including Shared Drive) using the latest (Raspbian-Stretch) distro then I will be forced into either using an old un-supported Yocto distro in my CEx... or possibly having to replace my old NAS for something newer.
Any help/guidance on this is much appreciated as usual thanks folks.
As mentioned above, the latest version of 'SMB' (cifs) network file sharing protocol supported by my NAS is SMB1.0. I know that the SMB1.0 client is disabled by default in Windows10 since 2018. I know very little about Linux but I can only assume that the SMB1.0 client is also disabled by default in the latest Linux distros like Raspbian-Stretch.
So the million dollar question here is... how do I enable support for the SMB1.0 client in the Raspbian-Stretch distro of Linux...?
Or can anyone think of any other differences between Yocto and Raspbian-Stretch that might be causing the 'Shared Drive' feature of my CEx to not work?
If I cannot get all of the CosmosEx features working (including Shared Drive) using the latest (Raspbian-Stretch) distro then I will be forced into either using an old un-supported Yocto distro in my CEx... or possibly having to replace my old NAS for something newer.
Any help/guidance on this is much appreciated as usual thanks folks.
-
- Atariator
- Posts: 28
- Joined: Wed Dec 16, 2015 4:15 pm
Re: CosmosEx 3.0 issues - can't get it to work [SOLVED]
I think I've finally cracked it . A 'Shared Drive' mapped to my old SMB1.0 NAS now works fine with the Raspbian-Stretch distro on my CosmosEx
The Stretch distro is different to the Yocto and Jessie distros in that by default it does not support mapping drives to an SMB1.0 fileshare. However it is possible under Stretch if you can specify 'vers=1.0' in the mount connection parameters. Unfortunately the 'Shared Drive' options screen in ce_conf.prg does not currently allow you to specify the 'vers' parameter. However you can 'inject' the vers parameter into Shared Drive settings by including 'vers=1.0' in the username field.
So to conclude... for anyone who might be interested... to connect your Raspbian-Stretch CosmosEx to an old SMB1.0 fileshare on an old NAS box you need to specify the following in the 'Shared Drive' options screen in ce_conf.prg , obviously adjusting the ip address to the ip address of your NAS drive and likewise with the username and password...
Shared drive settings:
--------------------------
Enabled : [*]
Sharing protocol : [Samba/cifs/windows]
IP Address of server : [192.168.1.?]
Shared folder path on server: [AtariShare]
Username : [AtariUser,vers=1.0] <------------ this is the crucial line
Password : [**********]
All thanks for this hack goes to some guy called @tin on the following thread...
https://www.atari-forum.com/viewtopic.php?t=31749
Happy Friday
The Stretch distro is different to the Yocto and Jessie distros in that by default it does not support mapping drives to an SMB1.0 fileshare. However it is possible under Stretch if you can specify 'vers=1.0' in the mount connection parameters. Unfortunately the 'Shared Drive' options screen in ce_conf.prg does not currently allow you to specify the 'vers' parameter. However you can 'inject' the vers parameter into Shared Drive settings by including 'vers=1.0' in the username field.
So to conclude... for anyone who might be interested... to connect your Raspbian-Stretch CosmosEx to an old SMB1.0 fileshare on an old NAS box you need to specify the following in the 'Shared Drive' options screen in ce_conf.prg , obviously adjusting the ip address to the ip address of your NAS drive and likewise with the username and password...
Shared drive settings:
--------------------------
Enabled : [*]
Sharing protocol : [Samba/cifs/windows]
IP Address of server : [192.168.1.?]
Shared folder path on server: [AtariShare]
Username : [AtariUser,vers=1.0] <------------ this is the crucial line
Password : [**********]
All thanks for this hack goes to some guy called @tin on the following thread...
https://www.atari-forum.com/viewtopic.php?t=31749
Happy Friday