Windows Server 2008 Internet shearing (not IIS)

September 5, 2013 at 22:54:51
Specs: Windows Server 2008
I am helping a business set up a network this is the current setup

Modem -- Server NIC 1 (184.XX.240.XX) WIN SER 2008 --Server NIC 2 ( -- 48 Port Switch (x2) -- Client pcs

the issue we are having is none of the clients have internet.
is there a way of shearing this with out using IIS?

these are the roles that are installed DNS what is required for the business to host there own DNS Records on there own server. We have DCHP installed for the clients to get a ip address. but they do not have internet access. also this is not a domain Controller. We are not using a router abd we are not going to.

is there any virtual routers or anything we can try?

thanks any help will be help full.

See More: Windows Server 2008 Internet shearing (not IIS)

Report •

September 6, 2013 at 06:57:20
The simple/smart method would be to buy a SOHO router and put it between the modem and the server. In fact, I would do so and also have it do DHCP for your network as well.

This would have the added benefit of reducing the load on the server and free it up for more important things.

Do you have a second DC configured for redundancy in case something fails on the primary one?

At the risk of sounding rude, I'm going to comment on your lack of capitalization when you type. It looks very unprofessional and well, it makes you look barely literate. If you work in IT proper grammar, spelling and punctuation should be an important part of anything you write. Whether it's a procedure guide, technical document, or a question on a forum like this.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

Report •

September 6, 2013 at 07:40:26
"We are not using a router abd we are not going to."

What makes you think you're not using a router?

Just because you don't have a dedicated SOHO router doesn't mean you're not using a router. Your multihomed Win 2008 server IS the router.

For small businesses, using a SOHO router like Curt suggests would be the most common and easiest setup, but not always the best setup. A set up from that would be to use a Linux server as the firewall and router. It could also easily be setup as the DNS and DHCP server.

BTW, SOHO routers are basically stripped down proprietary black box Linux servers.

message edited by FishMonger

Report •

September 6, 2013 at 09:36:36
How did we go from a misconfigured server to a Linux server for dhcp and dns?

Centi for your server to be a router you need to engage RRAS and setup NAT.

You need the workstations to point to the servers ip for both gateway and dns.

Last but not least you need to put the isps dns server ips in the forwarders [not to be confused with forward lookup zone]

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's

Report •
Related Solutions

Ask Question