Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Steve_M
Steve_M
Here to help
Member since Nov 15, 2022
Dec 9 2022
Community Record
15
Posts
0
Kudos
1
Solution
Badges
Nov 23 2022
6:32 AM
Typing the server IP (instead of the name) to access the network drive worked. The server name only works within the same subnet.
... View more
Nov 23 2022
6:28 AM
I was able to access the network drives by using the IP address of the server, instead of the server name. Granted, the firewall in the server is disabled, and I installed a new switch, so I don't know if using the IP address alone would have solved the issue from the beginning. Thank you everyone for the comments.
... View more
Nov 17 2022
7:54 AM
Here's a screenshot of the firewall.
... View more
Nov 16 2022
3:14 PM
Right now I have my server and another computer plugged directly into the MX using different ports. If I place them in the same VLAN I can access the network drives, but if they are in different VLANs I lose access. My guess is whatever is causing this is also giving me trouble with the Client VPNs.
... View more
Nov 16 2022
3:08 PM
I have an MX67 with a server containing network drives plugged directly into one port, and another computer plugged into another port. There are no switches involved. If I put the server and the other computer in the same VLAN, I can access the network drives just fine. However, if I put them in different VLANs, I lose access to the drives in the server. Does anyone know how I could address this? The use case for this would be to allow VPN clients in a different subnet to access the network drives.
... View more
Nov 16 2022
11:44 AM
I disabled the firewall but it didn't help. I did some tests and the Meraki won't let me access network drives that are not in the same subnet, even if they are connected to the same switch. I guess whatever is causing this is also preventing VPN clients from accessing the network as well. Do you have any idea of why this is happening?
... View more
Nov 16 2022
11:43 AM
I did some tests and the Meraki won't let me access network drives that are not in the same subnet, even if they are connected to the same switch. I guess whatever is causing this is also preventing VPN clients from accessing the network as well. Do you have any idea of why this is happening?
... View more
Nov 15 2022
1:34 PM
My drives are on the 192.16.24.0/24 subnet, and the MX IP is 192.16.24.1. I did a tracert to 192.16.24.1 from a computer currently using the Client VPN. Please see below.
... View more
Nov 15 2022
1:23 PM
We have a domain, but I'm using IP addresses. I ran a tracert on the MX public IP and took 4 hops to reach it, and it stops after the 5th hop after reaching the IP twice.
... View more
Nov 15 2022
12:56 PM
The VPN subnet is 192.168.1.0/24 and the network drive is located on 192.16.24.10. I created the rule below, but it didn't help.
... View more
Nov 15 2022
12:28 PM
Version MX 16.16, using L2TP. There are no custom rules defined in L3.
... View more
Nov 15 2022
10:00 AM
My company just ported to a new ISP which uses a Meraki MX67. I have a server which is a domain controller with active directory, a DHCP server, and which contains network drives. With my previous ISP, I used a SonicWall and had a VPN for my remote users to access the network drives. Once the VPN was connected I could "add a network location" as if I was on site. I have not been able to configure a Client VPN in the MX67 to work in the same way. I got as far as having a remote computer connect to the Meraki Client VPN using the Meraki Cloud Authentication, but I can't get the network drives connected. Any input on how I can get this configured would be much appreciated.
... View more
Labels:
- Labels:
-
Client VPN
My Accepted Solutions
| Subject | Views | Posted |
|---|---|---|
| 1245 | Nov 23 2022 6:28 AM |
© 2024 Cisco Systems, Inc.
