mchristo63
asked on
Network Project
Another question....
If I setup the following network, will the PC that are to to receive a ghost image be able to see the company backbone when finished imaging?
___ Company (DHCP) ______ 134.5.5.1 (NIC1-static)__ Server
134.5.5.x |
| 134.5.5.2 (NIC2-Static)
|
|_____________ Switch _____ PC (Staic IP from Boot Disk, DHCP when finished imaging)
|_____ PC
|_____ PC
The PC's will be ghosted with boot disk with static IP's. But when they are complete, they will be rebooted and need to receive a DHCP address. Will this work? Will the PC's be able to see the company backbone?
I know the following will work (below), but ghosting takes longer this way. If I isolate the PC's to receive the ghost images like the image above, it runs much quicker. I just haven't tried to connect a second NIC (image above) so the PC's will be able to see the company backbone when finished. What I am doing now is disconnecting the server from the company backbone, and connecting it to a dedicated switch, imaging the PC's and then reconnecting the server to the company backbone. Then i move the PC's to a differnet work bench and connect them to the company backbone. I thought if I could install a socond NIC, connect it to a switch to be used to image, this would still allow for company backbone connection and segment the ghost traffic.
___ Company (DHCP) ______ Switch ______134.5.5.1 (NIC1-static)_____ Server
134.5.5.x |
|_____ PC (Staic IP from Boot Disk, DHCP when finished imaging)
|_____ PC
|_____ PC |
If I setup the following network, will the PC that are to to receive a ghost image be able to see the company backbone when finished imaging?
___ Company (DHCP) ______ 134.5.5.1 (NIC1-static)__ Server
134.5.5.x |
| 134.5.5.2 (NIC2-Static)
|
|_____________ Switch _____ PC (Staic IP from Boot Disk, DHCP when finished imaging)
|_____ PC
|_____ PC
The PC's will be ghosted with boot disk with static IP's. But when they are complete, they will be rebooted and need to receive a DHCP address. Will this work? Will the PC's be able to see the company backbone?
I know the following will work (below), but ghosting takes longer this way. If I isolate the PC's to receive the ghost images like the image above, it runs much quicker. I just haven't tried to connect a second NIC (image above) so the PC's will be able to see the company backbone when finished. What I am doing now is disconnecting the server from the company backbone, and connecting it to a dedicated switch, imaging the PC's and then reconnecting the server to the company backbone. Then i move the PC's to a differnet work bench and connect them to the company backbone. I thought if I could install a socond NIC, connect it to a switch to be used to image, this would still allow for company backbone connection and segment the ghost traffic.
___ Company (DHCP) ______ Switch ______134.5.5.1 (NIC1-static)_____ Server
134.5.5.x |
|_____ PC (Staic IP from Boot Disk, DHCP when finished imaging)
|_____ PC
|_____ PC |
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Hi mchristo63,
You would have to enable routing on the server with 2 NICS. You might also need to enable DHCP relay agent on one of the computers in that subnet.
Cheers!
You would have to enable routing on the server with 2 NICS. You might also need to enable DHCP relay agent on one of the computers in that subnet.
Cheers!
ASKER
Would I ahve to setup a bridge so the second NIC sees NIC1?
mchristo63,
Some info on installing DHCP relay agents and getting DHCP working across routers. http://support.microsoft.com/default.aspx?scid=kb;en-us;257579
Some info on installing DHCP relay agents and getting DHCP working across routers. http://support.microsoft.com/default.aspx?scid=kb;en-us;257579
ASKER
I am trying to make this as easy as possible. CAn I just bridge the to NICS? Will that work?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Cool. That seems the easiest. So when I bridge, there is no problem if all PC are configured for the same network,correct?
The second NIC should be in a separate subnet, hence, separate network. It won't work if you are to bridge your 2 NICs and both of them are on the same subnet. In that case, the PC to be ghosted will be in a defferent network too. Like what Caltor mentioned, you should bridge the two NICs in the server, enable DHCP relay agent in the server. Additionally, you need to configure your DHCP server to serve the new subnet (the PCs to be ghosted). You will need to add a scope for the new subnet and use the IP of your ghost server's NIC 1 as the router in the new scope setting.
Hope this helps
Lapukman
Hope this helps
Lapukman
ASKER
Ok, so you can't bridge 2 NICS that are configured for the same subnet, then have to be differnet networks?
ASKER
Will bridging cause network issues on the main subnet? If so, will routing work better?
I am under the impression that the 2 segments will effectively become 1 subnet when you bridge them. I don't often use a bridge but I believe it will pretty much forward everything between the 2 segments to form 1 logical subnet.
In which case I don't think you will need a DHCP relay agent or an additional scope at all.
This is from the Windows XP help file on Bridging.
"With Network Bridge, you can connect LAN segments by selecting the appropriate network connection icons and clicking Bridge Connections. Equally easily, you can enable the bridge and add connections to it. The network bridge manages your network segments and creates a single subnet for the entire network. There is no configuration required, and you do not need to purchase additional hardware such as routers or bridges. IP addressing, address allocation, and name resolution is easy to do in a single subnet IP network."
In which case I don't think you will need a DHCP relay agent or an additional scope at all.
This is from the Windows XP help file on Bridging.
"With Network Bridge, you can connect LAN segments by selecting the appropriate network connection icons and clicking Bridge Connections. Equally easily, you can enable the bridge and add connections to it. The network bridge manages your network segments and creates a single subnet for the entire network. There is no configuration required, and you do not need to purchase additional hardware such as routers or bridges. IP addressing, address allocation, and name resolution is easy to do in a single subnet IP network."
ASKER