Wellicht dat jullie hier een antwoord op weten...
Had dit probleem gisteren toch 2 hele minuten opgelost, totdat RRAS NAT niet meer werkte...
Had dit probleem gisteren toch 2 hele minuten opgelost, totdat RRAS NAT niet meer werkte...
I have a Windows Server 2008 R2 32-bit server in a datacenter and a 64-bit at the office. The office connection doesn't allow incoming port 25. To make sure mail can be received, I've set up a user account in the AD and assigned it a fixed ip of 192.168.2.254. The VPN server doesn't have DHCP installed, so I've set a fixed host range of 192.168.2.5 till 192.168.2.254. The VPN server automatically takes 192.168.2.5, and when my mails erver dials in, it gets his desired IP as wel.
So far, so good.
I then added NAT for port 25 incoming to be rerouted to port 587 on 192.168.2.5 via netsh
netsh routing ip nat>add portmapping "name=Local Area Connection" tcp 0.0.0.0 25 192.168.2.254 587
After realizing I should have just mapped it to port 25, I've updated it with netsh
netsh routing ip nat>add portmapping "name=Local Area Connection" tcp 0.0.0.0 25 192.168.2.254 25
I have to say that at first, this worked, but I got a 5.7.1. when trying to deliver mail because the service via port 587 expects you to always identify first...
Too bad, because now it won't do any NAT routing. If I look at the NAT section, all the packet counts, etc. just stay at "-", I've tried rebooting and making custom firewall rules, changing the rules on the other end, but I can't seem to get it to work. I can still telnet in fine from the VPN server to the mail server over port 25, but the NAT routing fails.
I've removed the role, rebooted and added the role again, but all settings, etc. are remembered, so it has no effect... isn't there anything I can do or is there alternative software that works?
Ok, one bright spot; if you disable RRAS, it does clear its settings...
Observations so far: Every time you add a new mapping, the old ones are cleared and added one by one again (causes VPN disconnect when the VPN mapping is recreated). The total mappings field goes down to 0, and then up to 7 again (takes a lot longer then I expected). When I try one fo the two rules i created myself, I see the number of mappings decreasing; as if it crashed and is no longer active. Weird thing is that out of +/- 400 inbound and 400 outbound packets, the amount of packets rejected ramains zero.
To make sure that my firewall rules are properly configured, I tested with netcat to see if I can get in, but that's not the issue; connecting in works, it's really the RRAS/NAT section that messes up
Any ideas?
Thanks,
Nick.
[ Voor 21% gewijzigd door CMG op 09-09-2010 22:59 ]