network without sharing ?

February 5, 2009 at 03:27:12
Specs: Windows XP, pentium 4 1gb
I have searched the net for a solution to my problem but not found any real help, it may be a basic problem but i'm very new to this !
I need help to build a network, I have 6 clients (xp), 2 servers (win2008 and a win database server), 6 ADSL modem/routers, 1 unmanaged switch. My question is how do i set it up so that each client has LAN capability (static IP) yet retains indiviual internet access ? seeing as you can only specify one gateway and two dns servers if i give all the clients the domain server ip surely all traffic will be routed there and not to the individual modem. how do i seperate lan and wan requests is what i guess i'm asking ?

See More: network without sharing ?

Report •

February 5, 2009 at 06:11:02
You can't use a router for each machine. You only need one router and the one switch for the 6 clients and 2 servers. I'll take the other 5 routers :). All machines have to share the same internet connection and name servers but shares don't have to be created among the workstations. Each machine is joined to the domain, Use a .local name. Give each machine a static IP address on the same subnet. Disable DHCP. Let's say the router has an address of
All machines, including servers would have an address of 192.168.0.x X is between .2 and .254
Use the DNS addresses of your ISP.
They are set in TCP.IP properties of the LAN properties.

Report •

February 5, 2009 at 07:14:15
My question is how do i set it up so that each client has LAN capability (static IP) yet retains indiviual internet access ?

In order to achieve this, you'd also need 6 separate internet connections. An expensive prospect.

Also, you would need dual NIC's in each PC, one for the WAN (internet) and one for the LAN.

Then you would configure one NIC in each machine for the LAN and plug them into the switch. Finally, you would setup the last NIC on each for it's internet connection and plug it into the appropriate router.

Personally, I have to say doing what guapo said makes more sense. Which is, use one internet connection and one router with the switch plugged into the router's LAN port and clients/servers plugged into the switch.

If it were me though, I'd go with letting the DHCP server built into the router give out TCP/IP information to the clients. This simplifies things in the long run. Especially if you think you may be adding more clients or servers in the future.

You'd still want to statically assign TCP/IP information to any servers and network printers etc.

Report •

February 5, 2009 at 08:24:25
"Use the DNS addresses of your ISP. "

Sorry but this would be incorrect. Domain workstations need to point to the ms dns server.

"and two dns servers if i give all the clients the domain server ip surely all traffic will be routed there "

DNS doesn't work that way nor does routing.

"win2008 and a win database server"
There is no need for a wins server unless you have old apps that rely on netbios name resolution.

Given the exact question here is how I would set it up.

6 adsl modems to 6 adsl routers
all routers to switch - no dhcp from routers
Lan side of all routers configured for the same subnet but with a twist.
The twist is each pc would have a different gateway [these would be statically assigned]
For example:
pc1 gateway
pc2 gateway
pc3 gateway
pc4 gateway
pc5 gateway
pc6 gateway

All routers would go to a switch with all pcs connected also.

But this would really be expensive planning.

You would be far ahead of the game to get a dual wan port router, subscribe to two mega bandwidth pipes and configure the router to bind the two pipes together. Then just have tthe lan side as a normal setup.

Report •

Related Solutions

February 5, 2009 at 15:11:35
Why is using the DNS of the ISP incorrect? I've done it and it worked.

Report •

February 9, 2009 at 06:40:43
Thanks for the replies so far, reading
through i feel that 'wanderer's response is
offering the most help at present. I already
have in place 6 clients, 1d/b server and 1
2003 server, the 2003 server has had problems
(it was just a desktop in a previous life !)
and we are asking way too much it of hosting
the LAN and Web server side of things so we
have a new server coming (win2008)to replace
Up until now we have used static IP's
throughout and used the 2003 server as a DNS
server and each modem/router (paired to a
client) as a secondary DNS server the theory
being that the two IP's for each primary and
secondary dns server would handle the LAN and
WAN traffic ? It was working fine until the
2003 server had an issue then all of a sudden
it wouldnt let any client connect to the
(lan) domain so all the machines were
switched over to stand alones (hence the
individual internet accounts) and each
machine could carry on as normal but without
network capability (essential for our small
office !).
When the new kit arrives (Thursday) i would
just like to use all that i have available to
me to best effect to create a decent network
environment. At my disposal i have:

5 ADSL accounts
7 modem/routers of varying quality
10 clients (XP)
1 webserver (apache) running on an old
desktop machine with server2003
1 2008 server
1 unmanaged 16 port switch
1 printer

I plan to have a domain for the LAN as
".local" and each of 10 clients needs
internet access, preferably 2 machines per
ADSL line.

Hope this helps a little further with your
suggestion, i'm going to look more into teh
gatewat 'twist' mentioned above, keep your
ideas coming, its fantastic to finally get
some decent input on this !!

Report •

February 9, 2009 at 07:11:01
"Why is using the DNS of the ISP incorrect? I've done it and it worked."

If you are working with AD and workstations as part of the domain. the workstation dns entries point to the ms dns server. It is the only way you can have local dns name resolution for the workstations to find the servers or the servers find the workstations.

The ISP dns servers will never know this information.

Local workstations will work AFTER name resolution tries everything and then reverts to broadcasts [wherre are you AD server?]. You don't want your name resolution reverting to broadcasts as this causes delays and saturates the bandwidth.

unityjon putting the isp's dns entry as secondary is not uncommon but is only consulted if the primary dns server is down. As you experienced AD doesn't work then.

By design MS wants two AD/DNS servers. This way if one box goes down you still have AD and you still have dns.

MS dns forwarders tab is used to forward name resolutions the ms dns server doesn't know about. These point to the isps dns server.

I would trade your 5-6 adsl lines for one mega pipe. You have got to be paying $2-300 a month for that setup.

It does not gain you anything. You are just allocating bandwidth at a physical level instead of the industry standard way of using caching/bandwidth control servers. You get none of the benefits of fault tolerance/failover, bandwidth shaping or monitoring with your setup.

You appear to be raw on the internet.

You should have internet<> router firewall<>webserver<>router/firewall<> your servers/workstations.

Instead you have 6 hacker unprotected paths to your entire network.

You really need to understand AD and its design. "server suddenly had an issue" sounds more like a misconfiguration than a server failure.

Report •

February 9, 2009 at 07:44:46
I hear what your saying and thats what i'm
trying to amend, at present i have (sort of)
individual components that i tried to bolt

client(soft firewall) - router(hard firewall)
- internet

to this i added 2003 server (soft firewall) -
router (hard firewall) - internet to get more
than one client connected via AD and a Domain
and to provide us with a webserver to host a

the server developed problems after trying to
set up FTP using a java developers kit at
which point it died, lost all connections and
i had to re-install server2003 over the
existing install :o( as far as i am aware it
has wrecked the registry and who knows what
else to the point that when i a Domain its
fine on the server but no clients can connect
to the domain ("server cannot perform the
operation") and various other error messages
like "end point mapper has run out of end
points ?" but, when the server worked it
provided a great service, hence purchasing a
new properly equipped box with 2008 on it, i
plan to build the AD (we only have 6 users)
and configure the Domain and then start
adding the old clients to this and build it
up slowly.

none of this has happened over night, its
been in place for about 3 years. I've just
recently completed a microsoft AD course but
need to wait until Thursday this week for the
damn server to arrive. I am trying to get the
best possible solution straight on paper so i
have a road map of whats needed and what orde
i should do it so i disrupt the other users
as little as possible.

thanks for the help it is much appreciated.

Report •

Ask Question