Setting up my home network

[TDK2001]

I've been playing about with my setup below but cannot get any reliable connectivity between my lan machines and the net. Would anybody be able to advice me on setting up my networt properly?

1 x W2K3 Server, IIS, Exchange Server 2000
1 x 2600wi
1 x Desktop PC
1 x Laptop
1 x BTBroadband with dynamic ip
1 x domain registered with ZoneEdit which points to my dynamic ip

Should my server have enabled DNS, DHCP, WINS etc or should the router take care of the DNS and DHCP.

I would also like to host my own websites and mail server (not ideal on the same box I know but it ill have to do for now)

 

[lendpoint]

Hey!

Just set up a new domain. Let server handle all the network related stuff (Wins, DNS, DHCP) and use 3rd party application for internet sharing (I prefer Winroute Pro from Kerio software - it has port forwarding, NAT...).

If you need any further help/assistance let me know.

Gregor
hydralisk@email.si

 

[smilth]

just take care the router i think

 

[halukorhan]

Although I shared the Internet connection from the Local Area Settings at Windows 2k3 Server, the clients (users) are unable to connect to the Internet by using the shared connection at the server...

Do I have to manually adjust the Gateway and DNS Settings at the clients?

The IP of the server is 169.254.29.140

What is the reason for that?

Any help is appreciated...

Thanks in advance and regards!

 

[bradmg1]

First, I would get a router (Linksys is what I prefer). These normally come with DHCP functionality. If your playing around you may wish to disable that and run DHCP from the server. (Note: These types of routers are normally set with 192.168.1.1 as their internal address, thus your DHCP scope will have to be set in that range).

Next, I would not worry about running exchange and IIS on the same box. Looks like a very small network you have and one box should handle it easily.

DNS will be your biggest headache. I use a split brain approach. I have DNS running internally supporting active directory and my internal clients, it is not exposed to the public internet. DYNDNS.org runs my external DNS so people can access my web server and my e-mail functions properly.

Lastly, an IP of 169.###.###.### is a self assigned address. You need to set a static IP on your server.

 

[halukorhan]

Well, actually my question is:

How can I share the Cable Modem Internet on the Windows 2003 Server to the clients, without using any additional hardware?

Sharing Internet directly from the network card (NIC)? I also do not want to use 3rd party software like WinRoute!

Regards!

 

[bradmg1]

Ensure two NICs are installed. Once that has been accomplished you can share the internet connection by going to the advanced properties tab and selecting internet connection settings.

 

[halukorhan1]

Yes I made it like that but the Windows XP client can not browse the websites, although they are able to logon the server!

The IP of the server is 169.254.29.140

What is the reason for that?

 

[bradmg1]

169.254.29.140 is a self assigned address. Windows does this when it cannot receive an address through DHCP. Reset your modem and see what happens. If your using ICS your client machines will receive an address from the 192.168 range

 

[Silmeron]

As bradmg1 said, you'll need to put another net card in your server. Connect one to your cable modem, and the other to the hub/switch in your LAN. Use Internet Connection Sharing on the NIC connected to your cable modem. You can turn that on in the NIC's properties.

If you're trying to set up a network more similar to a company environment, then by all means install DHCP, DNS and WINS on the server to play with.

When you set up the DHCP scope, make sure you have DHCP automatically set your clients' gateway (which I believe is called "Router Address" - use the address of the NIC connected to your hub/switch [probably 192.168.0.1]). Also have DHCP set the DNS server to the same address (since you plan to run DNS) and *also* have DHCP set the WINS server to again the same address.

Basically when typing IPCONFIG /ALL on a client, you should see:

Ethernet adapter Local Area Connection:

Dhcp Enabled. . . . . . . . . . . .: Yes
IP Address. . . . . . . . . . . . .: 192.168.0.somenum
Subnet Mask . . . . . . . . . . . .: 255.255.255.0
Default Gateway . . . . . . . . . .: 192.168.0.1
DHCP Server . . . . . . . . . . . .: 192.168.0.1
DNS Servers . . . . . . . . . . . .: 192.168.0.1

Good luck!

 

[spazmahoney]

Get a broadband router. set it's inside interface address to 192.168.1.1. set the outside interface to dhcp for your isp's dynamically assigned ip address. statically assign the address 192.168.1.10 to your server and each workstation should have 192.168.1.11, 12, 13 etc...just make sure all have 192.168.1.xxx set each workstation and the server to have the default gateway of 192.168.1.1 and give them all the netmask of 255.255.255.0 learn more about ip addressing before doing dhcp, which you should set up on the 2003 server instead of a cheapy broadband router

Spaz Mahoney, MCSE