Server 2003 - configuration problem

[jeffg]

Hi,

I'm the junior admin in our group, hoping for some help with a configuration problem that I have been tasked to resolve. We use RIS to deploy machines to users. On a server that is not our primary RIS server, we have setup RIS for the purpose of testing/developing new images for a new platform that our client is considering.

The server that we are using has 2 NIC in it. One NIC card is connected to the rest of our network, and works fine (access to shares, internet, etc). We connected a switch to the 2nd NIC card, created a DHCP scope, with the hopes that we could work on test images without compromising the regular day to day builds on our primary RIS server. Client machines connected through the switch obtain IP's within the scope we created, but cannot access any network shares. The primary scope on our network is 172.29.1.30 - 172.29.1.253 and the scope we created is within the same range (172.29.1.10 - 172.29.1.20). This failed with the onboard NIC and with a PCI NIC that we installed.

Sorry for the confusing post - but does anyone have any suggestions on how to get the DHCP scope to see the rest of our network.

Thanks in advance.

Jeff

[fizban2]

if this is a testing environment, it would almost be better off not being available to the rest of the network, is there a reason that these machines need access to the rest of the network?

[jeffg]

The RIS process calls several scripts and writes to and from a SQL database that exists on another DC on our network. For the RIS process to complete - it must contact other servers on our network, as well as our clients trusted domain.

thx