I own one laptop (Inspiron E1705 running Windows XP Media Edition), one older workstation (Dell Dimension 4100 running Windows XP), one Poweredge 2900 Server(running Windows Server 2003 R2 x64), and a newer Netgear router. I also have DSL connection for Internet via Verizon.
Everthing is working, and I can reach the internet on all three machines which have the router in common. I need to setup the server as a true host, with the other two machines connecting as clients to the server. My DSL service seems to generate dynamic, changing IP's.
SInce I will be building and testing software/database scenarios, I believe I need a true "mini" version of a network with a domain, web server/services, and perhaps Active directory (also file sharing and printing). Some of this may require static IP's, I'm not sure.
I need your help in outlining the basic steps I need to take (and whether required or optional). In the past, if I've tried to use static IP's, then my DSL/Internet connection stops working. Need help with DNS and DHCP,etc. Do I need to register a domain? -secondayr question. Can I just unplug DSL and work on my "local" network with static IP's, can I switch back and forth,etc?
Any help or pointers would be appreciated.
In this case, in most default setups, the Netgear router provides NAT and does the IP address assignment to the client machines.
The router's manual should cover how to do one of the following:
Restrict the router to only assigning IPs within a portion of the subnet it will route. i.e. only assign 192.168.2.2-192.168.2.99 for example, and put all static machines in the 192.168.2.100-254 range
Set the router to always give the same IP address via DHCP to a particular machine based on its MAC address.
Any recent Netgear router can do either of the above, I use the second option with my WPN824.
I created both DNS and DHCP services, and created a domain, and Active Directory (I admit to using the wizard) on my server. Router issues aside, when I attempt to join my laptop (even when physically connected via docking station to my LAN) to the domain, it has a default workgroup of 'WORKGROUP' selected, and on the "Computer Name" tab, the "Network ID" button is grayed out.
Also, when I click "Change Name" the next dialogue it asks if I want to add a "primary DNS suffix" - I have no idea and what to put if so. And under the "Member Of" section, 'WorkGroup' is selected and 'Domain' is grayed out, as if its not possible to join my domain.
I am logged into an i.d. with Administrator rights, and totally lost. What gives? Is it a router issue only or do I also need to change a setting somewhere on my client (laptop/docking station)?
Entropy42
529 Posts
0
September 5th, 2006 13:00
In this case, in most default setups, the Netgear router provides NAT and does the IP address assignment to the client machines.
The router's manual should cover how to do one of the following:
Restrict the router to only assigning IPs within a portion of the subnet it will route. i.e. only assign 192.168.2.2-192.168.2.99 for example, and put all static machines in the 192.168.2.100-254 range
Set the router to always give the same IP address via DHCP to a particular machine based on its MAC address.
Any recent Netgear router can do either of the above, I use the second option with my WPN824.
pro223
4 Posts
0
September 25th, 2006 11:00