Routing issues for a network novice
-
you are using a public network as your "newcastle" network. the private range you intend to use is shorter then what you are using (ie: 172.16.0.0 - 172.31.255.255 )
it's rather unlikely that this is the cause of your issue, but you should change it anyways and if it still does not work provide us with some details (traceroutes/screenshot of firewall rules/static routes / …)
OK - I've reset the router, and I have adjusted the IP ranges as described above. Same thing. RDP works, but just keeps dropping out.
Here are my firewall rules on my virtual pfSense system.
No static routes in place. No gateways in use.
t.
-
I don't think this is a routing problem, if it was it wouldn't work at all.
In order to start troubleshooting this I would do a packet capture on both ends, and compare them to see if packets are being dropped, where and why
-
I did run a Wireshark capture but to be honest, I have no idea what I'm looking for in the trace. Is this the method you'd recommend for performing a capture? Anything in particular I should look out for?
t.
-
First thing would be to realize where the packets are dropping, so you would have to capture simultaneously on the diferent hops of your network (client side, both pfSense interfaces, server side), and then compare them
-
Thanks for the advice georgeman. If I perform packet captures, is there anything in particular I should look out for with regards to RDP dropping? Will Wireshark be intelligent enough to highlight drops/errors?
t.
-
OK - took some captures. The only one that seemed to look maybe odd (to my untrained eye!) is the one shown attached which was captured on my laptop in the HOME network on 10.0.0.100 which I am using to connect the RDP to the 172.16 'London' network. This happened about the time I got frozen and reconnected!
Can anyone tell what is wrong simply from this? Starting to pull my hair out!!
Thanks everyone so far!
-
I thought I would post my resolution in case anyone else experiences similar problems.
It looks like it is nothing to do with the routing after all and seems like it was all to do with my client. Executing the following command looks to have cured the error completely!
netsh interface tcp set global autotuninglevel=disabled
Since running this command on my system, I have yet to see the dreaded reconnect in Remote Desktop! Fingers crossed it lasts! Thank you all for trying to help. Much appreciated!
t.
-
are you seeing alot of Blocked entries on your firewall log ? Especially with proto: TCP-RA or TCP-A ?
If yes: are you natting the connection between one router to the next ? if yes: don't ;) -
Ah, thanks heper! Unfortunately I just noticed the issue re-occuring so I think I may have spoken too soon!
I did see entries like that now you mention it. I have not touched NAT on the virtual router so it is running pretty much as default (except FW rules etc) but I had set my home network pfsense to Manual Outbound NAT but have nothing configured in there for the LAN interface. Any pointers for things to check on?
Cheers.
t.
-
By default you will be NATting anything going from internal to WAN. Turn on manual outbound NAT on your 10.0.0.0/24 pfSense box, and delete the rules. You will likely need to add static routes on your physical LAN side, but this sounds like a NAT issue to me.
-
NAT is configured as described but still the problem persists :(
Any more suggestions?