Here is a example of the show mac- results. On port g6/32, there are 4 mac addresses, all of them are actually phantom macs. They dont have any entry in the arp table. The mac addresses are from Cray Communications and i suppect it has somethinng to do with the old IP phone. Both IEEE 802.1X authentication and MAC RADIUS authentication both provide network edge security, protecting Ethernet LANs from unauthorized user access.
Johnny SSH join:2008-12-31 | 2012-Jul-19 10:01 am RADIUS Mac Authentication Bypass on Cisco switchHi I'm not sure if this forum is only limited to Cisco WAN topics but I am having an issue configuring a Cisco 3650G to be used with FreeRADIUS and MAB. Currently I have a server running Linux (CentOS) and FreeRADIUS, and a laptop to test with. The switch should use the RADIUS server to obtain the correct VLAN configured for the particular MAC address.... I have managed to get the configuration for the FreeRADIUS server working fine and have had this verified too, in the meantime however, it has been pointed out that my switch configuration is wrong?? Here is the config: These are the errors I'm getting: The laptop is on interface G0/13 and should be configured with VLAN20 and of course get the IP address from the DHCP server configured within the switch itself. I have been reading up many different articles on MAB and Cisco including: »www.cisco.com/en/US/docs ··· p1196845 and »supportforums.cisco.com/ ··· Pass.pdf however nothing seems to be working :-( Can anyone help me? Thanks. |
2012-Jul-19 2:04 pm I found the answer to this which basically needed a much lesser config: And now it's working :-) | |
Da Geek Kid join:2003-10-11 ::1 | 2012-Jul-20 11:55 am cool Johnny SSH , Props for the update. |
Sharing Files
To enable File Sharing on your Mac, open the Sharing pane of System Preferences and select the option for File Sharing. Windows computers and Macs can then see your computer on the local network.
When you connect from a Mac using OS X Mavericks or OS X Yosemite to another computer using file sharing, your Mac automatically tries to use the Service Message Block (SMB) protocol to communicate. If SMB is not available, it tries to connect using Apple File Protocol (AFP).
To connect to a Mac or Windows computer that is sharing files on your local network, look under the Shared section of any Finder window.
You can also access local file shares from Open and Save windows and sheets.
To connect to a file server directly, use the Connect To Server feature of the Finder. Select Go > Connect To, and enter a URL, IP address or DNS name.
You can attempt to force a specific connection protocol (such as SMB or AFP) by using a valid URL. As long as the server you are connecting to allows the protocol you specify, the URL should work.
Advanced Options
![Reauthenticate port(s for mac os Reauthenticate port(s for mac os](/uploads/1/2/6/3/126359763/229520240.jpg)
If you want to limit which protocols can be used to connect to your computer using File Sharing, click the Advanced Options button in the Sharing pane. You can then select which protocols are used by your Mac. By default, OS X Mavericks and later automatically enable SMB and AFP for compatibility with Windows computers, Macs using Mavericks and Yosemite, and Macs using older versions of OS X.
Tips
- When entering a URL, the name of the shared disk, volume, or directory you are attempting to connect to (share name) must be specified. You are not prompted for it.
- You cannot type spaces as part of a share name when connecting. In place of any space in the share name, use %20 .
- When troubleshooting a connection issue, you can ping the IP address of the other computer using Network Utility. A successful ping verifies a TCP/IP connection between the two computers. This is an important first troubleshooting step when there's no response or a timeout for a connection attempt, since SMB connections involving a Mac require TCP/IP. However, a successful ping does not mean the SMB service is also available or working from the other computer.
- Check Microsoft support resources for information about setting up file sharing on your Microsoft Windows-based computer. These may include Help files installed on your PC, or the Microsoft online Knowledge Base.
- When troubleshooting an SMB connection issue, use Console in the Utilities folder. Console logs can help advanced users identify an issue. Some log files may appear only when logged in as an administrator.
- If you are connecting to a Windows SMB resource, check to see if your firewall is blocking TCP ports 137, 138, 139 and 445. After trying the above steps, you may perform advanced troubleshooting by inspecting log entries in the Event Log of the Windows SMB resource (if you have access to it), or the relevant logs in Console on your Mac.
- If you are connecting to Windows XP, make sure that the Internet Connection Firewall settings on your Windows computer are not preventing your connection. SMB uses ports 137, 138, 139, and 445. These ports should be open on the Windows XP computer. This may require 'Advanced' configuration of the XP firewall.
- Mac uses SMB only over the TCP/IP protocol, not the NetBEUI protocol.
- It may be necessary to contact your network administrator in some situations in order to grant access to your Mac from the SMB resource, or its host network configuration.
- Learn about connecting to legacy AFP services