|
#11
|
||||
|
||||
|
Old servers TCP/IP should look like this:
IP 10.0.0.2 SNM:255.255.255.0 gateway: prob 10.0.0.1 or 10.0.0.254 DNS 10.0.0.2 or 127.0.0.1 New server IP:10.0.0.4 SNM:255.255.25.0 gateway:same as above DNS: initially to join the domain..10.0.0.2 Once it has joined active directory and rebooted a few times logging into the domain....you can adjust it to look at itself for the DCPROMO act...and put the SBS IP of .2 for secondary DNS to help things going. I always show clients all the cool features of SBS....the flexibility of it's Exchange, and Sharepoint, and the remote portal. Once they see those features and you show how they can add to their functionality/collaboration, (esp since they've paid for SBS already)....you may find they want to use it. And they'll need your services for this...so NOW is when you can make extra money, and recurring money (be reselling stuff like e-mail filtering for them, domain management, etc).
__________________
Resident "Geek on a Harley" doing IT in Southeast Connecticut http://www.dynamic-alliance.com/ https://www.facebook.com/YeOldeStonecat |
|
#12
|
||||
|
||||
|
Thanks guys, it was
The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the D HCP service. This is not a recommended security configuration. Credentials fo r Dynamic DNS registrations may be configured using the command line "netsh dhcp server set dnscredentials" or via the DHCP Administrative tool. An error event occurred. EventID: 0x00000422 I ran this, rebooted both machines, and it worked just fine. Thanks for a reminder on the process and for shooting ideas on what caused this. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|