JorgeM is correct that we need more information on how your network is connected together. How the computers are connected will tell us how to guide you to fix this. For example, The way you worded the question implies to me that you have the server 2008 system connected to two netowrks. One with the clients on it and one that goes external to the internet. For that to work you would have to route traffic from the clients through the server. But I will save getting more specific till you tell us more.
Thanks guys, this is how my network is.....I av a server,server2008 installed on it and av two lan card installed on it as well, one of the lan card was connected to a modem and has an IP 83.299.4.76, subnet mask: 255.255.255.248, gateway: 83:229.4.73, dns:83.299.88.30 alt dns 217. and the second lan card has an IP: 192.168.0.4 subnet mask 255.255.255.0 and this was connected to the switch. DHCP was configure on the server as well with IP range 192.168.0.10 to 192.168.0.70. The clients get IP from the server and connected to each others but they could not browse the internet.
Ok then, for this to work, you have to enable Routing and Remote Access on the server and add the NAT service. You also have to make sure your DHCP client's default gateway is the private side NIC of the server. Feel free to post the results of ipconfig from a client to validate this for you.
I have a video tutorial on how to enable NAT on a Windows 2008/2008 R2 server that covers the steps on how to configure this service including a demo.
Hello, I av done that and cannot still browse, is there anytin I am still doing wrong? This is the ipconfig of one of the client Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
The problem here is that your client's default gateway (DG) is incorrect. If you are trying to pass traffic through the server, then the DG for your clients should be the server's private-side interface. You need to update your DHCP scope so that the proper configuration is provided to your clients. Here is what I gather from the information you provided... Take a note of the IP settings that are depicted in this diagram. This should be the correct configuration.
If this is a workgroup environment, you could configure the clients to use the external DNS servers. However, if you decide to install Active Directory services within your network, you will need to install the DNS role as well on your internal network. You would then need to update your internal clients to point to your internal DNS server(s) for DNS name resolution.
Summary: For this design to work, you must be running RRAS/NAT on the server, and your DHCP configuration must be updated.
My Recommendation: Rather than running NAT services on the server and having all of the client traffic pass through this server, I would highly suggest that you purchase at least a consumer based router and plug the switch into that router, then connect all of your network hosts into that switch. While Windows servers can function as routers, it is not the best approach, nor is it the most cost effective use for a Windows license.
Here is an example of a network diagram that will support Active Directory for a small office/home office type network. The server (192.168.1.200) would be running services such as Active Directory Domain Services, DNS, and DHCP. The DHCP service on the router would be disabled.
Here is an additional resource that may be useful to you. How IP Packets are Routed on a Local Area Network: Guide | Video