The ideal way to do this is to put the two of them on differently numbered subnets -- 192.168.1.x vs. 192.168.0.x, for instance, each with their own subnet mask. Also, unless the machine is actually serving as a router between the two subnets, it's not that easy for it to be a security hazard unless there is active file sharing or something of the like taking place.
Related Q&A from Serdar Yegulalp, WinIT
Frustrated admins have been dealing with extend.dat error messages since Outlook 97. Our expert sheds some light on this all-too-common Outlook error.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.