Another quirky item is that I can copy to file servers on the 10.0.0.x side of the router that are not DC's, but copying to the DC's it craps out. I've updated the NIC and teaming drivers to no avail.
On Tue, May 12, 2009 at 3:57 PM, Steve Ens <[email protected]> wrote: > hi Ben > We have some production machines on one side (192.x.x.x) that cannot see > the outside world (patches, AV software and the like). They are on our > broadcast production LAN and they've told us (internal LAN team) in no > uncertain terms that there must be a router in between. Then they went and > moved our graphics team into the broadcast LAN to access certain systems. > Linksys was what was in the cabinet at the time. Short term it was OK, they > could access mail, web etc. HOWEVER, they can access a different server with > no problems, so I am needing to update the NIC and teaming drivers on the > proliant tonight to see if that makes a difference. Otherwise I will create > a router using CENTOS or something along that line.... > Thanks for all the suggestions. > Steve > > > On Tue, May 12, 2009 at 3:49 PM, Ben Scott <[email protected]> wrote: > >> On Tue, May 12, 2009 at 11:54 AM, Steve Ens <[email protected]> wrote: >> > I have a private 192.168.1.x network within my 10.0.0.x LAN. It is >> > separated with a cheapie Linksys router. >> >> Do you actually need a segregated IP network? If so, what for? >> What's the application/goal? >> >> If you're just using the LinkSys to gain more ports, turn off the >> DHCP server on the LinkSys, and plug everything into the LAN side. >> The switch ASIC in those things isn't the best, but it will handle a >> heck of a lot more traffic than the CPU/RAM will. >> >> If you actually need an IP router, I'd agree with others that you're >> better off ditching the LinkSys. Those things are simply not intended >> to run at LAN speed. The CPU is a very low-power, low-cost model, and >> they have a tiny amount of RAM. Like a 100 MHz CPU and 4 MB RAM. >> It's not enough to run a decent IP router in software at modern LAN >> speeds. >> >> If you're on a budget, find an unused PC, toss an extra NIC in it, >> and install Linux or BSD. Instant router. Even a PC from a few years >> ago is likely to have a CPU faster than 1 GHZ and at least 512 MB of >> RAM. >> >> -- Ben >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ >> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ >> >> > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
