Building a Windows 2000 Microcosm? (separate ip networks)

[GREENCELERY]

We currently have a Windows NT domain w/ 20 clients all connected to a linksys 24-port switch and a linksys router. The Internet connection is ADSL with a single static ip and NAT.

We have two 24-port switches. (one is currently not be used)

The router is our DHCP server.

We need to build a parallel Windows 2000 domain network lab for a single domain controller running SQL2000. The test network will have two clients initially then all clients will be migrated over to the Windows 2000 domain.

The Windows 2000 Server needs to have the same NetBIOS name as the WINNT4 server (PDC on the existing production network) because our custom software has the NetBIOS name hard coded into the software.

What is the best way to implement a test environment so NetBIOS names and logon authentication will not conflict?

Can we request an additional static ip from our isp and setup two routers to the ADSL modem via hub, or can we purchase a router which will do NAT for two separate ip addresses. Can we introduce the test lab router into the current range of private addresses and assign the current production router as its gateway address.

I want the two networks to have Internet connectivity but exist separately without causing the current production network to fail.

Thank You

 

[doomhamur]

Hello,

A router with a trusted port and a dmz port that can be separated will work. the watchguard firebox 700 can share a single internet connection with 2 different networks and those networks will have separate firewall policies. the firebox 700 runs about $1400 Doomhamur
Network Engineer
"Certifications? we dont need no stinking certifiaction."