the dhcp clients cannot access the internet but can access the shared resources on the server, ie they can see the server in network places and access shared folders. the static clients can access the internet but cannot access the server, see it in network places or access shared resources from the server. The dhcp clients have three dns servers setup in the dhcp scope, which when I run ipconfig on the clients that information is there; and they still can't access the internet. primary dns is my server, secondary and tertiary are isp dns servers. Now for the statically assigned clients the only dns server I listed on their tcp/ip configuration is my server, nothing else; and they access the internet just fine. **************************************** Now, I have been told that I should have my server setup with a static ip. But if I do not use one of my public ip's for the server then how do I use my public ip's? Can the dhcp and dns server be set up using a static private ip? How about my ftp and web server? I would think they do need a public ip. Now can I set up public ip's for those server roles while having a private ip set up statically for the server itself? Cause that was one of the issues I had earlier, the nat could not be disabled on my previous linksys router and so my public ip's were being translated into one private ip for the whole of my lan. Now with the router/modem in bridged mode all my public ip's come right through and when I make a request out the ip that goes out as the one that made the request is the ip of the computer that made it. also, since I want to host my own web site I believe I do need to use a public ip and have the isp's dns servers point to my public ip when the get a request for the website name. In that situation especially I do belive I would have to have a public ip. Which brings me back to a question I made earlier in this post. Can I have the server's ip be a private one and set up a public one just for its web server role?

0

First off NAT = network address translation. Your router should be doing NAT. (public to non public IP's/diferent subnets.) thats what NAT is for. Take the router out of bridged mode. lets go back over my post and add in Curt R's post here, and add in some notes. ........... wow long post there.... .... I take it you have the server behind the router? .... then why does it have a public IP? 1. configure the router with your public IP info on the WAN side. (internet side) 2. set a static IP on the server for your LAN (plugged into local network side of router) IE.. router LAN Side 192.168.1.1 server 192.168.1.2 subnetmask 255.255.255.0 gateway 192.168.1.1 dns 192.168.1.2 (if dns is configured on the server) 3. reconfigure you DHCP scope..... scope range 192.168.1.100 - .??? dns = 192.168.1.2 (only DNS you need, your server handles the DNS for the clients) ......... now add in the good info from Curt R. .... You will want to forward the DNS server (192.168.1.2) to your ISP's DNS servers. This way, your DNS handles all requests inside the local zone (LAN) and forwards requests outside the local zone (internet) to your ISP's DNS for resolution. (This is in your forward lookup zone) ...... Now for some new info!! Port forwarding in the router... Lets say your router has a WAN IP... 216.216.216.216 Your ISP/DNS host should be pointing everything to that IP.... 216.216.216.216... Now I take it you have 1 server? so I will use the above 192.168.1.2. in the router port forward port: 80 - 192.168.1.2 --- For a web server. 21 - 192.168.1.2 --- For your FTP 3389 - 192.168.1.2 --- For RDP (nice for remote admin)(this is the default port for terminal server) 25 - 192.168.1.2 POP3 If your running exchange(and people pop off mail) 110 - 192.168.1.2 SMTP If your running exchange Try the above and you will find everything works... May take 24-48 hours for the DNS for your web and FTP to filter through the internet once you have the host correct it.

0

I apologize if I am frustrating you guys, like I said, at least to me this has been a difficult problem to solve. Now, thank you for the explanation but I did already know what NAT meant. I don't doubt that what you posted would work, but I hesitate to do that because in your examples you use just private ip's. If you are saying that I should not use public ip's at all I ask you why? From what I understand, using nat on the router would mean that any request sent by any client or the server, to the internet would look like one ip, I don't know if I am remembering correctly but I believe that to be my gateway ip ( Which I also assume to be what you are referring to as Wan ip, if not please if you could explain further). And according to the port fowarding you asked me to set up on the router any request back would go through the router to the server, which would then distribute that request to the appropriate client using its dhcp server role. Now by that rationale I don't really need public ip's. But that begs the question; Why would somebody need public ip's then? At the moment I have a few to use and would like to know if there are any advantages to having them, otherwise I might just give them back and stick to private ip's, especially since everything seemed to be working fine before and is very buggy now. The reason I ask all this is also because I want to be able to do it either way, with public or private. I may be wrong, but don't many businesses own some public ip's and would therefore have to deal with similar problems as I face now, but often in a much larger scale. If I'm right on that then all I am doing is trying to prepare myself to at some point be able to set that up for some business, maybe even other than my own and get paid handsomely for my results. So once again, I apologize if I seem to be hammering a point you feel is irrelevant. As you can see, it is not irrelevant to me and I would be very thankful if you would just indulge me and help me find a solution either way. Thank you very much for your help so far

0

My god man.... Go to a networking class!!! Your WAN IP is the Public IP provided to you from your ISP. (The gateway they provide you is a router on their network) Large businesses have more then one public IP for many reasons.... Multiple web servers, terminal servers, ftp servers and such. Multiple locations. You will find out most of these companies will also have large Cisco routers that can have more then 1 public IP assigned to it, and can programmed to handle NAT, port forwarding, and all other network traffic depending on what IP the traffic comes in on. So yes you need at least 1 public IP. In your case you don’t seem to know much about NAT, subnets, port forwarding. First thing you learn about “subnets”…. Different subnets are used so that you can separate networks on the same infrastructure. So you could have a network at 192.168.2.? and a network at 192.168.1.? on the same switch, and they cant see each other! (would need a good switch for this… prefer a 3 layer) Now the problem you are experiencing with PC’s not seeing the server is subnets! Your server is on a public (lets say) 216.216.216.216 with subnet 255.255.255.??? your network is getting DHCP IP’s 192.168.1.???? with subnet 255.255.255.0. …. See an issue there???? I do…. 192.168.1.??? with a subnet 255.255.255.0 … means only talk to PC’s in the 192.168.1.??? range…… Well how the heck can they talk to your server then??? Do the above and you will find it works.

0