10-08-2018 10:44 AM - edited 07-05-2021 09:16 AM
I have a Cisco 2504WLC. 2 Networks few AP's. Private Network and Guest Network.
Guest Network has no issues so there's no use bringing it up.
Network type is a Home/Small Buisness Network with Windows Domain.
My issue is any devices connected on the Wireless LAN are unreachable. They can connect and browse the internet, hassle free however.
For example, I have a wireless laptop, it cannot find the name of the \\FILESERVER2\ if it searches for it[Device Connected on Wired LAN]. It comes back inaccessible, but if I went \\10.0.0.5\ it finds it perfectly fine.
However if it is on the Wired LAN via Ethernet \\FILESERVER2\ works perfectly fine.
If a printer is connected to the Wireless LAN, (Using an older 1142N in Workgroup bridge mode) it cannot find it. Not even with the IP address.
P2P Blocking Action (Disabled) - Is the only thing I can think of. They are all on the same subnet aswell.
In otherwords: A device connected on the WiredLAN is accessible only by the IP address of the Wireless Device on Wireless Network, it does not work by using the computer name \\FILESERVER2\. If the computer is connected by Ethernet. No issues.
If a device is connected by the Wireless Network, Devices on the Wired LAN can not see the devices on the Wireless LAN even though they are on the same subnet.
You can scan the Wireless Network using a mobile phone to see any devices connected. However only by the IP address will show. Unless the device is wireless and using a AP Configured as a WGB.
Thoughts?
Solved! Go to Solution.
10-16-2018 05:46 PM
Hi Dillon, just to close the loop on this one, the issue was that multicast was not setup right, after setting up multicast the cast destination shows up on wireless.
10-08-2018 04:40 PM
Hi,
Have you check name resolution is set up correctly. Are you using WINS or just DNS? Are you using DHCP to assign addressees for both network?
Thanks
John
10-12-2018 09:34 AM
10-12-2018 05:18 PM
10-13-2018 08:13 PM
can you verify code on WLC, AP model, also are you running interface group ?
10-14-2018 08:24 AM
10-14-2018 02:23 PM
the software version on WLC ?
paste "show sysinfo" from controller CLI, if its ok with you.
Since your Guest is working as expected, lets not worry about it, to keep our focus clear.
I am assuming:
Access works between 2 devices when you connect 2 devices are on wired on same subnet.
Access works between 2 devices when one device is on wired and another on wireless on the same subnet
Access it does not work when both devices are on wireless.
Additionally if possible, perform a wireshark capture on one of the macbook connected to wired accessing a resource (preferably TCP).
connect the same macbook on wireless and perform same capture accessing same resource.
attach both pcap files.
Thank you
10-14-2018 04:13 PM
10-14-2018 04:15 PM - edited 10-14-2018 04:21 PM
Responses by the question.
Access works between 2 devices when you connect 2 devices are on wired on same subnet.
-Any Device connected by Ethernet can communicate with one another with 0 Failures providing both are connected by Ethernet. All Ethernet connections are one subnet.
_____
Access works between 2 devices when one device is on wired and another on wireless on the same subnet.
-Access works when the device in question is connected by Ethernet. The wireless device can find it without issues only by using the IP address and not the hostname. You can use either or if on Wired Eithernet.
-Flipping it the other way, if the wired device is connected by wireless, it will not find it by it’s host-name or IP address.
-Wired Devices cannot see the Chromecasts, wireless printers (Which have been converted to Ethernet for now), or wireless laptops.
Access it does not work when both devices are on wireless. Correct.
10-14-2018 04:17 PM
10-14-2018 08:01 PM
OK, i wanted to check any known bug, but did not find any.
It does seem like an odd behavior, my house runs on 2504, most of my devices are Wireless and I heavily use P2P never had any issue, although I am using 8.5.135.0 unlike yours, since 8.5.120.0 is deferred.
See if you can upgrade, if you have support on your 2504, you might as well engage TAC and let us know, what where the findings.
on windows you will have challenges with wireless capture unless you have right adapters, but if you can please share the capture logs.
10-15-2018 08:36 AM
10-16-2018 01:49 AM
10-16-2018 05:46 PM
Hi Dillon, just to close the loop on this one, the issue was that multicast was not setup right, after setting up multicast the cast destination shows up on wireless.
10-16-2018 06:37 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide