Hello, first of all this is my first time buying Raspberry Pi 3 Model B (Jessie) and so far I'm very impressed. So, I am currently experimenting Pi to work as "thin client" using Remmina to RDP to my office's Terminal Server Windows Server 2012 in CISCO network. The CISCO network is currently divided to different segments: 10.1.30.xx for servers, 10.1.10.xx for LANs, 10.1.70.xx for WIFIs.
The Terminal Server IP 10.1.30.xx The Terminal Server Gateway 10.1.30.1
The Raspberry Pi LAN IP 10.1.10.xx The Raspberry Pi LAN Gateway 10.1.10.1
The Raspberry Pi Wifi IP DHCP 10.1.70.xx The Raspberry Pi Wifi Gateway 10.1.70.1
So these are the results of my experiment: - Raspberry Pi using LAN as same segment with the Server: giving the Raspberry Pi IP as 10.1.30.xx and the gateway as 10.1.30.1. Works perfect and I can remote desktop using Remmina to the Windows terminal server perfectly - Raspberry Pi using Wifi: with DHCP giving the Raspberrt Pi IP 10.1.70.xx and the gateway is 10.1.70.1. Works perfect and I can remote desktop using Remmina to the Windows terminal server in segment 10.1.30.xx perfectly - Raspberry Pi using LAN in segment 10.1.10.xx is giving me headache. Giving the Raspberry Pi IP as 10.1.10.xx and the gateway as 10.1.10.1. I can ping to either 10.1.30.1 and 10.1.30.5 but couldn't get the Remote Desktop working. Usually IPs from any other 10.1.10.xx in windows should be able to remote to terminal server 10.1.30.xx just fine
My current eth0 LAN setting in /etc/dhcpcd.conf is:
Cisco DNA Software Demo Series - Cisco ThousandEyesRegister nowWednesday, May 12, 202110:00 am Pacific Daylight Time(San Francisco, GMT-07:00)SaaS applications and cloud-based services are increasingly critical for on-campus users, but they can be challen...