HELP ME! Im having a Server 2003 Nightmare :/

Microsoft Windows server 2003 enterprise
May 13, 2010 at 17:41:09
Specs: Windows Server 2003, NA
I've tried following about 20 tutorials now to set up my Server 2003 machine. I want it to provide DNS and DHCP service to a local area network and share a wireless network connection.

At different stages I have had it providing an IP to my test client. I have also been able to connect to the internet using my test client, but only when I manually entered the IP and DNS details on the client.

Probably the most useful guide I've tried following was http://www.tomshardware.com/reviews...

When it got to the part where I was to test my DNS server with nslookup my results were not as in the tutorial. I may have made some incorrect choices because the tutorial is not step-by-step, but also because the tutorial seems to only deal with one NIC. SO I got confused about which numbers to put where.

At the moment my wireless connection is set up as:

192.168.1.20
255.255.255.0
192.168.1.1 <= My wireless router

192.168.1.1
. . .

And my internal network connection is set up as:

10.1.1.1
255.255.255.0
. . .

. . .
. . .

Is this correct?

If so what should I do next? I removed the DNS and DHCP services for the time being since they weren't working properly anyway.

Thanks


See More: HELP ME! Im having a Server 2003 Nightmare :/

Report •

#1
May 14, 2010 at 13:22:37
You have your gate way on a different subnet than your wireless. They must be on the same subnet. Also, some silly questions:

Did you disable the DHCP on your Wireless Router?
Did you setup a DNS forwarder on your Server?
Did you setup an Address Pool in your Scope?
Did you setup the Router in your Server Options?

Don't forget you need to setup a reservation for you Wireless Router in your DHCP server to prevent conflicts.


Report •

#2
May 14, 2010 at 13:38:18
I would suggest CtrlZ you evaluate your objectives.

There is no need for the wireless to have anything to do with the server. What are your usage expectations? In other words do you expect to give guests wireless access or access to the server via wireless?

You commented about a single nic. Why would you consider internet access thru the server? That is much more complicated and so far I can't see any reason for you to do so.

Please provide what your objectives are so we can advise you properly.


Report •

#3
May 15, 2010 at 15:01:33
Thank you both for your replies.

My objective is to run a monthly LAN party for up to 23 guests. I essentially wanted to use the server as a router bridging two networks. My guests will be a part of the internal network, and the server will connect them to the external internet. This idea was based on two reasons: 1. It would help a lot if the internal sub-net was always the same for certain programs we use. 2. We don't have a permanent venue and so the internet connection always changes. In this particular case it is a wireless connection where I don't physically have access to the room with the wireless modem, and my users do not have wireless.

I had thought this was a good solution since we already had the server, whereas buying an actual CISCO or other router could cost a lot of money. I also thought that a computer would give me the flexibility to add other utilities such as traffic shaping. I have since been made aware that setting up PC's as routers is much more hazardous than with actual routers because PC's can more easily be hacked into.

Somebody pointed me toward keeping my server as a game server and setting up a DD-WRT for my purpose. I am now investigating DD-WRT and also 'Tomato'.


Report •

Related Solutions

#4
May 16, 2010 at 11:16:48
A server as you describe along with using wireless will make for very poor game play/lan party.

The wireless modem has to support ddwrt so I doubt that is a good avenue for you.

Given your criteria there is no reason for you to have a router. You need a wireless card in the server to talk to the wireless modem.

You engage RRAS between the servers wireless card and the wired card. You properly setup dns and dhcp services on the server.

You have to determine what ip subnet the wireless modem is providing. Your dhcp server has to be configured to a different subnet as also the servers wired nic. Set the dhcp to auto update dns. In the servers dns you have a forwarders tab [not to be confused with the forward lookup zone]. You enter the isp's dns server entries here. Dhcp provided dns entry is only that of your servers lan card ip as well as that entry in the servers wired lan tcp/ip dns entry


Report •

Ask Question