Internet Access problem on WS2012 RDS Server with thin clients


hello everyone,

i have configured ws2012 server follows :

base-server ( physical server) ws2012 & hyper-v

this ads/dns , domain controller.

external virtual switch configured ip address : 192.168.0.250. hosted on server lan card. server has single lan card. dns ip provided isp. gateway ip given server 192.168.0.254 ( firewall lan port).

i have cyberoam firewall internet connection. lan port ip 192.168.0.254. server , firewall connected passive switch.  the thin clients connect rds server connected switch.

i have configured virtual server rds server. server has ip 192.168.0.244. connected virtual switch mentioned above. gateway given 192.168.0.254. dns 192.168.0.250 ( dns server).

i have 40 thin clients , given ip addresses in range 192.168.0.100 150. gateway them configured 192.168.0.254. dns dns server i.e. 192.168.0.250. 

the windows firewall in servers off. 

the issue faced :

for internet access, every user should authenticated either firewall or adserver. when first user tries access internet, presented cyberoam login screen. once authenticated, gets internet access. 

but user logs in after not asked internet access credentials cyberoam firewall. gets free access. situation same whether authenticate user on firewall or through ads server.

i had escalated cyberoam asked me talk microsoft in ws2012 tcp ports not open default(?). if firewall off, server accept communication on port. 

any suggestions? related ws2012 /rds issue?

from :

shekhar-nsk

hi,

in order connect internet need have dns record pointing rd gateway's fqdn , tcp port 443 forwarded on router/firewall internal ip address of rdg.

if using rd web access need configure rd gateway settings in remoteapp manager.



Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file