How to fix UGREEN NAS access issues over Ethernet Mac Studio?

reaoo wrote:

want to solve the connection UGREEN NASync DH4300 to connect directly to Ethernet cable by Mac.

how to setup DHCP-assigned addresses, though static addresses?

1. You can't have it both ways. It's either static, or DHCP assigned.
2. The NAS and the Mac can't have the same IP address. The screen shots show the Mac having the same address as the NAS. This is wrong and will of course cause issues.
3. You can set up the Mac to act as a DHCP server so it hands IP addresses to directly connected devices such as the NAS by enabling Internet Sharing in System Settings.
4. There is no way to configure static addresses on the Mac since it lacks the "router" panel. You would need to configure a static address directly on the NAS first, while you can connect to it on the network. This will instantly sever the network connection to the NAS though. You would then connect it directly to the Mac instead of through the router, and if the Mac is set to the same IP address range but a different IP, then you should be able to see the NAS and its config page using the address you gave it.

If your current network configuration with your NAS & Mac is as follows (as I believe this is what you are describing in your post):

• Mac Studio connected to the local network by Wi-Fi.
• UGreen NAS directly connected to Mac Studio by Ethernet.
• UGreen NAS is NOT connected to the local network by Wi-Fi.

If all of these are TRUE, then this configuration WILL NOT work as you planning for it to do. Again, the reason is they are each configured to be on a different subnet AND your Mac is not performing as a router.

So, to be of any assistance to you, we need to know the following about your current local network:

• For your network router:
  • What is its LAN-side gateway address?
  • What is its Subnet Mask?
  • Is it configured as a DHCP server?
• For your Mac Studio:
  • Is it configured as a DHCP client? If IPv4 Configured = Using DHCP, then it is.
  • What is its current IP address?
  • What is its current Subnet mask?
  • What is its current Router IP address?
  • What are its current DNS Servers IP addresses?
• For your NAS (You currently have it configured for manual IP addressing. That means that it is NOT acting as a DHCP client, and therefore, will not be getting any IP address info from your router):

Please answer these questions. If you don't know or are unsure, then I agree with MrHoffman that you need to seek help from a local area networking expert to sort this out for you.

I’d use DHCP, at least until I better understood IP networking, subnetting, and routing.

Wire the Mac and the NAS to the RJ45 connections (usually) available on the local router.

Ok, looking at the second image, you have configured your NAS with static local IP addresses with your local network router/gateway @ 192.168.2.3 and the NAS @ 192.168.2.2. This is fine as long as the NAS is connected to the gateway by either Ethernet or Wi-Fi. However, if I understood correctly from your original post, you disconnected the NAS from the gateway, and then, connected it by Ethernet to your Mac.

The DNS server address @ 192.168.1.1 would indicate that there is another network device (router, server, Raspberry Pi running Pi-hole, etc.) that is providing DNS service. This address is also on a different network subnet, so any communications with it would have to go through the router/gateway.

reaoo wrote:

want to solve the connection UGREEN NASync DH4300 to connect directly to Ethernet cable by Mac.

how to setup DHCP-assigned addresses, though static addresses?

You will pick either the use of DHCP, or pick static (fixed, manual) IP address.

DHCP picks an address from its pool and hands it to the client. For static IP, the IP addresses you choose and manually assign to the client (NAS or whatever else) should be outside the DHCP pool, and must not conflict with any other IP clients in use.

How to set up your local DHCP server and clients depends on your DHCP server which is presumably available in your router, and how the NAS can acquire an address in the NAS documentation.

Check the documentation for your router and your NAS.

I'm going to assume three things here. Please correct me if I assume wrongly:

• Your Mac is situated such that it cannot directly connect to your router by Ethernet ... correct?
• Your wireless router or wireless access point is situated such that your Mac is not getting a strong signal, and more importantly, a high data transfer rate for its connection ... correct?
• Your NAS does not natively support Wi-Fi (most don't) ... correct?

When you moved your NAS, so that it can be directly connected to the Mac by Ethernet, the NAS no longer is accessible from the Internet ... and why you can't access it via the Internet nor locally via a web browser. That's because it is no longer connected to your local network ... only to your Mac. Your NAS must have a local IP address assigned to it. Typically, that would be from the DHCP service provided by your local network router.

If I assumed correctly that where your Mac & router are not near each other, you are basically left with having to use a Wi-Fi connection between the Mac & the router, AND that this NAS needs to be directly connected to the same router by Ethernet.

Alternately, you would need to acquire a local mass storage device that you can connect directly to your Mac for file storage ... but not have a web-based interface to it.

What is your subnet? You are showing 192.168.2.2 and 192.168.2.3 and 192.168.1.1, and these are only in the same subnet with 192.168.0.0/16 (255.255.0.0) configuration or such.

Which is a possible configuration with various gear, either because the gear provides different subnets for different network sections, or it uses a /16 (255.255.0.0) or such. A /16 would be somewhat unusual. It’s usually a /24 (255.255.255.0) for a network segment here.

Otherwise, 192.168.2.2 needs a router (192.168.2.3?) to get to the 192.168.1.1 DNS server or DNS resolver.

You can also see if somebody can either visit and configure this network for you, or bring the gear somewhere and have them configure it for you. Or there may be some IP networking sessions around your area.

So what is your question?

Do you have the same issue, or do you want to offer a solution.

If you want to offer a solution, you can post it here in the thread you created. The old post has been locked due to age and the OP having resolved it.

Typical would be ethernet cable to your router, from the Mac and separately from the NAS.

But the speed expected with all that depends on your Ethernet speeds, and your Wi-Fi speeds. And your NAS I/O speed.

It would be more usual to run DHCP-assigned addresses, though static addresses can work.

Whether the NAS is slow or painfully slow depends on various factors, such as the network connection speed, whether the Wi-Fi and wired network is correctly configured, and on details such as whether the HDDs are in RAID 5 or the perception of slowness can arise from HDDs being vastly slower than SSDs.

Here is why a hard disk is so much slower than an SSD — thismin the context of an iMac with HDD — and writes to a RAID-5 HDD NAS are even slower:

• https://discussions.apple.com/docs/DOC-250005142

You’re going to get to learn more about IP network configurations, and about that UGREEN NAS.

@Tesserax thank you for replaying

My Mac is connect with Wi-Fi only, and I setup NAS with static local IP addresses as you mentioned at old post.

file transfer direct use Ethernet.

But I can't used the NAS as cloud or remote access and I can't see NAS through (find.ugnas.com)

I used NAS app

the NAS Device show red light

will share the shot screen to look

only I have the router and connect the Mac through Wi Fi.

But I can't used the NAS as cloud or remote access and I can't see NAS through (find.ugnas.com)

I used NAS app, the NAS Device show red light

want to solve the connection UGREEN NASync DH4300 to connect directly to Ethernet cable by Mac.

how to setup DHCP-assigned addresses, though static addresses?

First of all thank you for helping me

data transfer connection is good but the ugreen link is disconnected I think because of gateway and DNS IP

you can check the shot screen