![]() Another post spoke of a conflict between the Apple nic and Cisco routers/switches, which is what we have. This chipset apparently offers connectivity that the Apple nic lacks. I did not want to revert to 100 Mb transfer speed and found instead an Anker USB 3.0 Gb adapter that uses ASIX ax88179 chipset. ![]() I then ran across a post where use of Apple's 10/100 USB NW adapter worked 100% of the time. Still no change with one particularly bad computer. I have tried knocking out all apple's smb2 implementation through terminal. I have had users connect to Win 2008 R2 server shares using cifs. This is for a Mac OS 10.9.x design studio. We have had a persistent problem with smb connections dropping out. Oh, and I've made some research before posting this, so I really don't know how to proceed with this. At the same time, a friend of mine is having exactly the same problem with his macbook. I think that this issue is related to Windows Server 2012, because this doesn't happen if I connect to a shared folder in 2008 server, but I'm not sure because I made a test with another macbook and a Windows computer and they work fine. I've also tried creating a file on the OS X to force SMBv1 connection and was no use. I've tried using an Active Directory login to connect to this share and that also worked just for some time. I've already tried using cifs, but that worked for some time and the problem came back again. The thing is, in this same environment I have a Windows Server 2008 and I've made a test creating a folder and sharing it just for test purpose and my SMB connection on my Macbook didn't drop one single time. After the VPN client is connected, it obtains a VPN IP as 172.30.50.1.Ĭonfiguration screenshot of the Omada Gateway in standalone mode.Ĭonfiguration screenshot of the Omada SDN Controller.I have a Macbook Air with OS X Mavericks 10.9.2 that is dropping connection to a Windows Server 2012 share. For example, if LAN IP is 172.30.30.1, then the VPN IP Pool should be 172.30.X.Y.įor example, here we set up the LAN IP of the VPN router as 172.30.30.1/24, and the VPN IP Pool as 172.30.50.1 – 172.30.50.20 (for standalone mode) or 172.30.50.1/24 (for Omada SDN Controller). Note: If you use a Class B network, make sure the second segments of the IP addresses of the LAN IP and the VPN IP are the same. Modify the LAN IP and VPN IP Pool to Class A or B addresses, so that the routing table generated after connecting to the VPN server, ensures that it can access the remote network.Ĭlass A network include IP addresses: 10.0.0.0 to 10.255.255.255 while Class B network include: 172.16.0.0 to 172.31.255.255. Set up Class A or B network for the LAN IP and VPN IP Pool. After connection, all traffic will be forwarded to the VPN server, Mac can access both the Internet and remote network. Go to System Preferences – Network, find your VPN connections, go to Advanced, check “Send all traffic over VPN connection”, click “OK”, then click “Apply” to enable the settings. Since the Windows client works fine, we can adopt the same configuration, and the Mac should also work fine. Enable “Send all traffic over VPN connection” How to solve this problem? Here are two options. The difference causes that the Windows clients may work fine, but Mac clients cannot access the remote network. Why is it like this? Actually, after the Windows clients are connected, all traffic will be forwarded to the VPN server by default while Mac clients will still forward Internet traffic to the local gateway. But you may find after connecting to the VPN server, the Windows clients are working well, but the Mac clients from Apple Inc. With L2TP over IPsec, the VPN client can securely access the remote network resources.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |