- Pulse Secure Community
- :
- About Nate_
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
since
10-29-2017
10-29-2017
Nate_
Occasional Contributor
6
Posts
0
Kudos
0
Solutions
11-27-2008
02:02:PM
Will, Look at the original issue... To access (via RDP) the NC clients through the juniper from say, Computer C, in the NC access rules i must specify the IP & Src ports of computer C, NOT the destination of the NC IP ranges & 3389 Every rule in the NC access rules ONLY ONLY applies to the non-NC host, whether its the destination or source of the traffic, it will always be the non-NC host details. i.e. Network connect host: 1.1.1.1 Server on the inside LAN: 2.2.2.2 If i want to connect FROM the Server (2.2.2.2) to the NC client (1.1.1.1), the rule required is: "Resources" 2.2.2.2:<src port> It is NOT 1.1.1.1:3389
... View more
11-11-2008
01:29:PM
Jickfoo, I'm trying to lockdown the source port the RDP session is coming from on the internal network, not a firewall/vpn etc. I know there's a few reg hax out there to lock source ports down to ranges for other protocols, just not sure if there's one for RDP. If you cant lock it down, then you'll have to allow a heap of ports through the VPN both to & from the internal networks.
... View more
11-09-2008
04:04:AM
I've had this one going for a while & no luck... until tonight! (even Juniper didnt have any answers when i raised the case)... The SSL VPN firewall rules ALWAYS apply to the non NC machine... ALWAYS!!! If you RDP from the NC to a Server, the rule is: Resource IP: Server Resource Port: RDP If you want to RDP from a machine on the inside LAN to the NC Client (to support remote users!!!) Resource IP: Server Resource Port: RDP connection source port on the server!!!!! --> i.e. randomised high port!!! The next question is, how to lock down the source port of RDP connections so i can secure it a little... anyone know any reg hax etc to force source port connections?
... View more
09-15-2008
03:09:PM
Solved! Upgraded both devices to 6.2R1 & this fixed the issue. The clients now install fine.
... View more
07-14-2008
03:53:AM
Got a few issues with Network Connect & a specific build of lappy running Vista. Network Connect cannot install the adapter, so upon login, it tries, fails & then tries, fails etc over & over. Its a HP L1910 Laptop running Vista SP1. Anyone know of any specific app/service that stops auto install of a network adapter? I've upgraded to the latest IVE release & it works on other Vista clients & all our XP machines.
... View more
07-03-2008
06:53:AM
I'm having the same issues... i was pretty sure it was working with: tcp://<helpdesk ip's>/<mask>:3389,5900 however its now not working.... however if i put * for the port, it works! but i use the VPN for access restriction, so i'd have to redo the firewall again. It seems for Inside --> NC Clients it needs * for ports?!?!? I'll do some sniffing tomorrow....
... View more
Latest Tags
No tags yet
© 2017 Pulse Secure, LLC. Use of this website assumes acceptance of our Legal Notices and Privacy Policy.
Pulse Secure has updated its Privacy Policy effective June 28, 2017.
