It's almost like the router is pushing all packets to this IP sort of by default but I've come across anything like that.
Add the 3388 port forwarding rule anyway and that works.īut I'm flummoxed how RDP is being routed to the existing server without any rules on the Netgear router/firewall? The existing server is on 192.168.100.250.
Expected to see a couple of existing entries for RDP and the bespoke app on port 81. No problems.Ĭome to look at the port forwarding rules on the Netgear and hit a brick wall.
Netgear genie port forwarding windows#
Change the port via the registry, add a new rule into Windows firewall for port 3388 - check RDP works from the LAN. We're installing a new Dell server running Windows 2012 and one of my early tasks is to get remote desktop working - on a different port to 3389 because that's assigned to the existing server. So nothing particularly unusual and as with many small businesses, records of configuration are non-existent. There is also a bespoke monitoring program running on the server accessible via port 81. The Windows server has RDP configured, accessible via their single static IP address. I'm helping out a small brewery business which has a pretty simple network consisting of a Netgear WNR1000v3 router, a Windows 2003 server, couple of network printers and laptops. I'm pretty familiar with firewalls, routers, port-forwarding etc after 20 years of managing networks but this one has got me flummoxed.
0 kommentar(er)
