My system is wired as follows:
--Comcast-->Modem/Router/NAT---10.0.1.xxx ---->>Linksys/Router/NAT ----192.168.0.xxx ------->> Local Network
With this setup My Win7/XP system with their Linux dual boots have been able to live amiably together. I am in the process of getting CIFS working across everything, but needed to get some bugs ironed out. Win7 has Homegroup services disabled.
Problems started on the newer 64 bit Linux system, which was mirrored in the Win7 sister boot. It was firing up with an IP of 192.168.56.x - well out of the shadowing range of the Linksys. Both boots were only seeing the Comcast router, which somehow was being provided a 192. rather than a 10. numeric address. Networking on that machine was thoroughly putzed. Internet worked fine.
Somehow my suspicions as to cause are leaning to VBox, which has installed its own routing table entries.
It appears to be influencing non-VM networking. Has anyone run into anything similar - and is there a solution to the problem.
The temp solution here was to disable the Comcast modem/router and fire up the system. It now takes a dynamic address of 192.168.0.xx. -BUT- the 192.168.56.xx is still in the routing tables.
The machine is still having problems networking - its slow at configuring, but can now see most of the network at least. (Comcast has been turned back on).
The obvious solution would be to go to fixed local IPs on the machines, but this has in the past presented its own set of problems....