gumbygaz Posted August 2, 2016 Posted August 2, 2016 Morning, Hope somebody can help, we had our smoothwall installed last week and also changing ISP. We've got new external IP Range, so having to changing the new IPs to forward to our Remote Desktop Server but can't get it to work. Smoothwall have remoted and said traffic is getting through the smoothwall to the server but not getting any response. The server is up, working fine internally and was fine on the old IP this morning. The RDS server's firewall is off, so that shouldn't be stopping anything. Is there something stupid I'm missing out. Anything I need to change since changing the IP? Want to get this working before shifting our Exchange & Frog to the new IPs. If I go to the page in the browser, I get a blank white page with a smoothwall favicon but nothing else. Adding /rdweb etc I get Apache server page not found response (I assume the Smoothie?) Any clue/tips/tests anybody could throw my way would be appreciated. Cheers
mikkydoos Posted August 2, 2016 Posted August 2, 2016 (edited) Sure its not the config on your ISP's router ????? EDIT: Ignore that. Just re-read the post properly. Its internal. ooppsss Edited August 2, 2016 by mikkydoos
BaccyNet Posted August 2, 2016 Posted August 2, 2016 I've just done the same thing today - BTNet and a new S8 appliance. I had to change the gateway on the server (exchange in our case) to the Smoothwalls internal IP otherwise whilst the server got the request it never sent the reply. Didn't have the problem before due to the 'interesting' way the LEA system was setup..... 2
FN-GM Posted August 2, 2016 Posted August 2, 2016 When we make any changes to NAT on our Smoothwall we need to reboot the smoothwall for the changes to work properly. Might be worth a try? 1
gumbygaz Posted August 3, 2016 Author Posted August 3, 2016 So reboot didn't work, mainly because I'd not been directing traffic to the smoothwall (gateway was still set to the old router! durr!) and had a rogue port in the port group so it was redirecting to the wrong port. Just got to get the MX relay bit working, but I think that's just RM needing to allow us on the new IP and happy days! phew! Thanks
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now