Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About HSHan
Community Record
10
Posts
0
Kudos
0
Solutions
Badges
Sep 21 2023
11:37 AM
I see that I am referring to IPv6 rules. Thank you. Do you happen to have any references or information regarding IPv4 traffic for port forwarding or NAT?
... View more
Sep 21 2023
11:11 AM
I am experiencing difficulty adding an inbound rule to allow specific traffic from the IP range 168.86.128.0/18 and ports 10000 to 60000. However, it seems that Meraki only allows options for "Any," "IPv6," and "VLAN." Can anyone provide advice or a solution for this situation?
... View more
Sep 16 2023
9:12 AM
Thanks for clarifying my question. I will contact ISP to remove the tag from those APs.
... View more
Sep 15 2023
10:08 AM
That's what I thought. Thanks, WW. The strange thing is, the Wi-Fi ports goes down when I switch from VLAN 1 to VLAN 10. If it's managed by the ISP, it shouldn't matter what I set, right?
... View more
Sep 15 2023
9:42 AM
The screenshot below shows the configuration window in Meraki for assigning VLANs to each port. *Unnecessary information has been concealed for clarity. This setting allows Meraki to apply the specified VLAN when configuring a particular VLAN on the respective port. As additional information for ports 2, 3, and 4, there are company WiFi access points (APs) configured on these ports with both VLAN 10 and VLAN 50. These access points enable communication between the two VLANs. However, according to the settings on the screen, the wireless APs connected to ports 2, 3, and 4 should be assigned to VLAN 1. However, Upon checking the assigned IP addresses, it appears that VLAN 10 with the IP range 192.168.1.0 is being assigned instead. Consequently, communication is occurring as if the devices connected to port 6, which is allocated to VLAN 10, are communicating with the printers/users. Of course, the CS team and QA team connected to ports 8 and 9 are currently using different network subnets, which is why they cannot access the printer. Here's a question for you. Question 1 Even if I change the VLAN ID on Meraki ports 2, 3, and 4, there is no change in the assigned IP addresses. In other words, no matter which VLAN I set, only the IP addresses from VLAN 10 are assigned. (Doesn't this seem unusual?) The access points connected to ports 2, 3, and 4 are products provided by the ISP, and I don't have administrator privileges on them. Therefore, I have no way of verifying how VLAN 10 and 50 are assigned within those access points. Currently, the only method I have is to check the assigned addresses from the incoming traffic. Question 2 Is there any significance to the "Native" setting configured on ports 2, 3, and 4? Question 3 How can I remove 'Native" config? or Is it causing any problem if I remove it?
... View more
Sep 14 2023
4:03 PM
Hey, amabt Thanks for taking time to read my question. The firmware was updated a while ago. (Current version: MX 18.107.2) Actually, I had no problems using the printer before with the current VLAN setup, but something happened that I don't even remember. The printer suddenly stopped communicating over the VLAN. It could be a device issue, but I want to verify whether this is a device issue or a problem with the functions. I searched for 'NBar' in the event log, but found no results. Any ideas?
... View more
Sep 14 2023
1:27 PM
Yes, I changed it to 'Any,' but the issue remains. The strange thing is that I can't use Telnet from 192.168.1.191, which is on the same network as the printer, but I can print from this laptop. It appears that the Telnet feature is not enabled on Meraki. Do you know how I can confirm?
... View more
Sep 14 2023
11:01 AM
Yes, currently, all sources are set to deny. I've added an 'Allow' rule for VLAN 10, which is connected to the printer. However, I'm still unable to Telnet from the other VLANs.
... View more
Sep 14 2023
10:32 AM
Hey, Raphael. Thank you for taking the time to look into my issue. I attempted to connect to the printer with Telnet, but unfortunately, I was unsuccessful. Could you please let me know what settings or configurations I need to enable in Meraki to make this work?
... View more
Sep 14 2023
9:52 AM
Device: Meraki MX 100 VLan ID 100: 192.168.100.x (Printer installed here) VLan ID 200: 192.168.200.x VLan ID 300: 192.168.200.x Printer ID: 192.168.100.64 Test PC: 192.168.200.1 I have utilized the port-based VLAN feature to set up several VLANs on my network and connected the network printer. However, I am encountering an issue where I cannot print from the test PC (192.168.200.1). Do you recommend setting up a printer server to facilitate printer sharing across the VLANs? I initially anticipated that the printer would be shared, at the very least, among VLANs connected to the same Meraki device. =================================== < 2nd part >=================================== I added an 'Allow' policy to the Meraki Firewall as suggested. To summarize, I can ping from both IP ranges (192.168.125.x and 192.168.1.x), BUT I encountered an error. C:> Connecting To 192.168.1.64...Could not open connection to the host, on port 23: Connect failed I'm not sure why I need to test Telnet to verify printer sharing functionality. Is this test still valid and accessible even if I don't have a printer server?
... View more
Labels:
- Labels:
-
Administrators
-
Other
© 2024 Cisco Systems, Inc.
