About IT_Tropolis

IT_Tropolis · ‎08-05-2021

Hi: MX68W. This morning users came into office and all of a sudden cannot connect to SSID 1. All users/clients affected. Tried renaming the SSID but still cannot connect. Tried forgetting the wireless network on a Windows 10 client but still cannot connect after re-discover. SSID 2 still allowing connections (different VLAN). Enabled SSID 3 and it's allowing connections. Any ideas why SSID 1 would just all of a sudden disallow connections? Thank you, Bob H.

IT_Tropolis · ‎07-02-2021

This issue is back. I've seen it in (3) different Windows 10 Build 19042 devices in the last two days. I guess using rasphone.pbk is a workaround but hopefully Microsoft will fix it soon. Is Cisco putting pressure on Microsoft to fix it?

IT_Tropolis · ‎07-02-2021

This issue is back. I've seen it in (3) different Windows 10 Build 19042 devices in the last two days. Is Cisco putting pressure on Microsoft to fix it???

IT_Tropolis · ‎07-02-2021

Hi Jason: Did you ever find a solution to this issue? I've seen this on (3) devices in the past 2 days. Thanks, Bob H.

IT_Tropolis · ‎07-02-2021

I just started seeing this issue again, on (3) different Windows 10 computers in the past 2 days. All 3 are Windows 10 Build 19042 but that may be a coincidence. VPN working then all of a sudden it won't connect. Authication method set to General Authentication. Changing it to Username and Password caused the Adapter settings to have the Security tab option for protocols greyed out so neither PAP nor CHAP are checked. Fixing the Adapter settings resets the VPN authentication from Username and Password to General, and round and round we go. Was their ever a fix for this issue besides using a 3rd party VPN s/w, i.e. did MS fix it?

IT_Tropolis · ‎10-30-2020

Hi @GreenMan Is there a way to workaround/cfg. for this scenario to work, i.e. for Client VPN users to be able to access LAN resources when coincidentally their outside LAN subnet from which they're connecting is same as the office LAN subnet? Thank you!

IT_Tropolis · ‎10-30-2020

Hi: User has MacOS machine. User connects to Client VPN successfully. They obtain Client VPN IP address and I can ping their IP. But they cannot RDP to their computer on the LAN via IP address or connect to the LAN Intranet. They cannot even ping IPs on the LAN. Split tunneling is NOT cfg. and they can connect to Internet sites, and those sites see their public IP as the office IP, not their home ISP public IP. If user physically takes same MacOS machine to a Starbucks or another house it works as expected, i.e. they can RDP to their machine at the office and they can connect/open the Intranet site. At location w/issue, they have Frontier FIOS w/an ARRIS NVG468MQ router. It uses 192.168.254/24 network. The office coincidentally uses the same LAN subnet 192.168.254/24. Is this the cause? Thanks for any insights!

IT_Tropolis · ‎06-02-2020

Hi: I have numerous users working remotely on MacOS devices connecting to a web site hosted behind an MX84. I've configured the MX84 with a 1:1 NAT rule allowing their public IP. It's been working with months without an issues. As of yesterday, they can no longer connect, i.e. https://MyWebsiteBehindMX84.com returns error page: Server is unavailable now. Please try again later or contact your administrator. Their public IP has not changed and we verified another non-MacOS device on their LAN can connect. I'm thinking a MacOS update may have caused this issue, perhaps something to do with IPv6? Any insights are greatly appreciated! Thank you, Bob H.

IT_Tropolis

Community Record

Badges

All of a sudden cannot connect to SSID on MX68W

Re: Windows 10 version 1903 Client VPN issue

Re: Windows 10 built in VPN Client will not hold settings

Re: Desperately need a Meraki VPN Client!!!

Re: Meraki's fault? Microsoft's?

Re: Client VPN connected but cannot RDP or connect to Intranet

Client VPN connected but cannot RDP or connect to Intranet

MacOS "All of a Sudden" Cannot Connect using firewall 1:1 NAT Rule - Maybe ...

MacOS "All of a Sudden" Cannot Connect using firewall 1:1 NAT Rule - Maybe ...