From: "~~Alan~~" <alan.shepro-NOSPAM******.com>

| Let me shed some more light on this and see if a solution might work.
|
| I am experimenting with a Windows 2003 server in the house to learn more
| about creating and manageing an ADS Domin. My home network consists of the
| server, 2 WinXP Home systems, 1 MAC OS latest and greatest, and 2 WinXP pro
| systems. I am connected to the internet with one of Verizon's Westell 327W
| modem/wireless router combo devices. Here is my idea.
|
| 1. Configure the westell's DHCP capablities to provide a scope of only 3
| address 192.168.1.100-102 with a lease time of say 99 days so the addresses
| stay with the home and mac systems over the long term
|
| 2. Configure the server with a static (private internal lan) address, and as
| an ADS domain controller with a DNS Zone
|
| 3. Configure the server's DHCP capabilities with a scope of
| 192.168.1.110-120
|
| 4. Release all leases on all workstations and shut them down
|
| 5. Boot the 2 WinXP Home and Mac systems and let them get their addresses
| from the Westell's DHCP
|
| 6. Boot the 2 WinXP Pro systems and they should get their address from the
| Windows server DHCP a long with the DNS stuff from the server.
|
| Any thoughts?
|
| ~alan
|

Turn off the SOHO LAN appliance's DHCP server and use the Win2003 DHCP server.

--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm