Cannot connect in finder using mac

[Daankuster]

Hello,

I am new and not very knowledgeable regarding servers etc... I have been using my 211J with my previous mac and macbook pro without any issues. I am able to connect via the internet (from "outside") etc. However, with my new IMAC (others were stolen from us..) I cannot connect to my synology "locally" via finder. I am running the latest DSM version (3.1-1748) and using mac os X (10.6.. I am using an airport extreme which is connected to my cable modem to provide a wireless access for the IMAC. The synology is connected via lan cable to the airport extreme.

the problem is, in finder IF it sees the synology it cannot connect. It takes a long time for it to try to connect and then i get a message which states that either the IP is wrong or server is not available. In finder all is selected regarding "showing servers etc".

please help me?! this is driving me nuts! and I am sure it is a scilly setting i did not set. Oh I have the win and mac sharing service enabled.

please help?

rgds,
Daan

[thunderbird]

Did you try to connect to the NAS using "go to server" (I think it's APPLE + K) and manually typing afp://username@NAS-IP/sharename?

[rapidisimo]

Isn't there a button labeled "Connect As" on the top right part of Finder?
Click it, enter your login info for the NAS (a user you have created in DSM) and from then on you shouldn't have to login again(save it in your keychain).

[Daankuster]

Thanks for the quick reply guys! However, both solutions do not work. tried it before.

[antonmuller]

If you say you hooked up your DiskStation to an airport extreme, there is necessarily an IP address assigned to your DS by the AE (check in the AE settings : if you are hooked to your cable modem with DHCP, AE is automatically set up to distribute IP addresses). This address varies if you change environment/machines. To know the IP address assigned to your DS use a free software for Mac such as IP Scanner. It will show all the IP addresses of the devices connected to your Mac, wirelessly or via LAN cable.
Once you get your DS's address, try connecting from the Finder ->Go>Connect to server and enter afp://ipadress, for instance afp://10.0.1.4 if IP Scanner gave you 10.0.1.4 as IP location of the DS, then you should be able able to mount the DS volume using your usual username/password
Good luck!

[Ambassadeur5000]

Have you checked the Synology firewall? I had exact the same problem... I saw the DiskStation but could not connect.

[cyaque]

I´ve the same problem

[chadforeman]

I have the same problem.

[spdfrx]

Me too... Neither Finder nor Time Machine can find the volume.

[Chipster27]

I had the same problem but discovered I had checked "deny" access in the DSM firewall. When I changed it to "allow" Finder connected with the drive again

Thanks to Ambassadeur5000 for the suggestion.

[vmaxhp]

I have the same problem and I do NOT have the firewall enabled.

[new_109+_owner]

If you use terminal to connect to the Synology, what do you get? eg


$ telnet diskstation 548
Trying 192.168.0.2...
Connected to diskstation
Escape character is '^]'.

This shows the DS is available and serving.

What do you get?

[nonsoloinglese]

I am having a massive issue trying to get my ethernet connected iMac to connect with the DSM software. When I switch my iMac to WiFi, i have no issues. However when it is on Ethernet it creates issues.

Using Synology assistant you can see it, you can ping it on the terminal but you cannot for the life get the DSM Web UI up or a disk mounted on the iMac.

Using wifi on my macbook air I am able to access the UI and mount the disks quickly without any issues.

I have a Time Capsule that acts as a WiFi router and DHCP server and this is connected to the same router that my iMac connects too, so there is no issue there.

Both the MacBook and the iMac are running 10.7.3 and the iMac is able to operate on the network so it can't be an issue with the physical cable.

Any help greatly appreciated!

[nonsoloinglese]

I had set jumbo frames manually on OS X and this was causing the connection issues. Once switched to manual it worked.