Evilted: You posted your last message as I was writing mine. Rather than re-editing mine, I'll post it as is.
-------
Could we handle one item from the original post at a time.
Quote:
when I have a machine on 10.10.1.0/24 I cannot remote desktop to a virtual windows server (sitting on linux vmware server), which is set to 10.10.12.201 netmask 255.255.255.0
|
I assume the client on 10.10.1.0/24 is a windows client. You probably have a gateway device or computer on 10.10.1.1 or 10.10.1.254. Is the gateway setting correct on this client?
What is the device, a router or another computer? If it is a router, did the routes to the other subnets survive the power outage. If it is a Linux computer, please post the outputs of "ifconfig" and "route". Doing so in [ code ] [ /code ] blocks will preserve the formatting.
Post the output of "cat /proc/sys/net/ipv4/ip_forward". It should be "1".
I once had a problem getting forwarding to work when I used my laptop to share a wireless connection. I found that I needed the "ip_conntrack" module loaded. Then it worked.
It may go by another name now, depending on your kernel. Please post the output of "lsmod | grep conntrack". I wasn't using NAT on the laptop, just forwarding packages. Since you mentioned a power outage, I thought perhaps that either the ip_forward wasn't set to "1" during the reboot, or maybe you are missing a needed kernel module. Either could prevent packets from being forwarded from one interface to another (including virtual interfaces).