hmcnasty
asked on
SBS 2003 Rebuild question
If I have an SBS 2003 environment with multiple DC's and I need to rebuild my SBS machine how will it effect the other DC's when I put it back into the Domain?
Wes
Wes
ASKER
The SBS machine that I just fixed.
I put 2 new nics in cause the ones I was using were USB (temporary) and I didn't want that. It came with Broadcom onboard but those never worked. So I orderd 2 new ones and installed them last night.
I configured the nics alright but I'm sure SBS was thrown off a bit so I wanted to run SBS again to fix any problems and have it "bind" to the new nic cards and work out ony other kinks but of course it won't let me run it as you saw in my other question last night reagrd me having to be an administrator to continue the set up.
Aslo
After it boots up if I try to open AD it says it can 't find it the DC then I'll go into DNS and re add it to the domain the and AD will come back. Wired stuff like that.
I when I put this thing into production I just want it to be right ya know and I'm concerned that there are just too many problems at this point that are beyond me at this point.
I built the SBS as a primary DC then I built 3 other DCs (same domain) to go in other locations. My plan was to use a static VPN connection from the Primary DC to the other DC's in the domain for AD and exchange. 2 of the machines are already built using server 2003 and were replicating fine with the SBS primary DC. I can remove the SBS and they will still function on there own, of course DNS isn't entirely happy but at least thier running until I can get this machien fixed somehow.
My pan is to get all these machines built then delpoy them in their locations and set up the static VPN through ISA but I don't want to do anything else until I knwo this SBS machien is gonna function properly.
Wes
I put 2 new nics in cause the ones I was using were USB (temporary) and I didn't want that. It came with Broadcom onboard but those never worked. So I orderd 2 new ones and installed them last night.
I configured the nics alright but I'm sure SBS was thrown off a bit so I wanted to run SBS again to fix any problems and have it "bind" to the new nic cards and work out ony other kinks but of course it won't let me run it as you saw in my other question last night reagrd me having to be an administrator to continue the set up.
Aslo
After it boots up if I try to open AD it says it can 't find it the DC then I'll go into DNS and re add it to the domain the and AD will come back. Wired stuff like that.
I when I put this thing into production I just want it to be right ya know and I'm concerned that there are just too many problems at this point that are beyond me at this point.
I built the SBS as a primary DC then I built 3 other DCs (same domain) to go in other locations. My plan was to use a static VPN connection from the Primary DC to the other DC's in the domain for AD and exchange. 2 of the machines are already built using server 2003 and were replicating fine with the SBS primary DC. I can remove the SBS and they will still function on there own, of course DNS isn't entirely happy but at least thier running until I can get this machien fixed somehow.
My pan is to get all these machines built then delpoy them in their locations and set up the static VPN through ISA but I don't want to do anything else until I knwo this SBS machien is gonna function properly.
Wes
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok I got through that ok..Thanks. Doesit matter that the nics are not named Network Connection and Server Area Local Connection any more?
No, it shouldn't... however, you do need to make sure that the binding order is correct. The LAN NIC needs to be above the WAN NIC in Network Connections > Advanced > Advanced Settings...
Jeff
TechSoEasy
Jeff
TechSoEasy
Jeff
TechSoEasy