|
#1
|
||||
|
||||
|
Router Help! Static IP
Let me see if I can explain this well enough!
I was just recently issued a static IP from my ISP. The ISPs tech came in swapped the traditional cable modem for with a new router. They gave me all the addressing info WAN Address Subnet Mask Router Address DNS Servers Along with it they gave me the static IP stating that hosts needing a static IP must be in the range of the new static IP That all make sense to me! Here's where I get lost! I have been using a dlink office router to handle DHCP to handle addressing for an internal lan that uses the standard IP range 192.168.0.xxx. I have lots of theory in networking with static IPs, but no practical experience. Somewhere between learning about it in class and setting it up I have taken a wrong turn and gotten lost. For some reason I was under the impression that I could set up my the router with the new static IP use it as a gatway to their pass through router so it would be easier to locate over the WAN for remote access. Then use my router to handle DHCP the the same as always. I have 10 computers that access the internet through this router as well as share files in a workgroup. Do I need to get an individual static IP for each client on my lan in this new IP range? If I set up the router to use the new IP for the WAN settings, can I still use the 192.168.0.xxx IP range for LAN DHCP and at the same time access the WAN or internet? Hopefully I have given enough info and made questions clear!
__________________
Have you ever stopped to think, then forgot to start again ?
|
|
#2
|
|||
|
|||
|
I also have the curse of a static IP. I only have three computers on my home network, but I had to configure each computer on my D-Link router manually, using the a range of IPs given to me by my ISP.
__________________
Dimension C521; Athlon x 2; 2 GB RAM; Vista Ultimate 32 bit; 320 GB HD; DSL connection;; Eset Smart Security v3; Spyware Doctor; Windows Defender; Spyware Blaster; Acronis True Image v11. |
|
#3
|
||||
|
||||
|
Quote:
So, if you have machines that access the internet and are not an internet visible server, then you can continue to use NAT on your router and give them a 192.168.0.x IP. If, you have a machine that you want to be an internet visible server (web, email, ...), then you want to give it one of your ISP's static IPs.
__________________
cmd /k ipconfig/all [use to start ipconfig from 'Run'] cmd /k ping <some website, like google or yahoo> [use to ping 'www.google.com' from 'Run'] |
|
#4
|
||||
|
||||
|
Z1p
That's what I thought, maybe they just don't have their router configured properly or gave me the wrong info because once I set up my router with their static WAN info, none of the computers on my l LAN could access the internet. As far as internet visibility, I had intended to use port forwarding on my router to handle any remote access to the computers and devices in the office. I had be using VNC Server to access computers from the internet before we got the static IP but it was a pain with a dynamic IP because the WAN IP was changing all the time.
__________________
Have you ever stopped to think, then forgot to start again ?
Last edited by Smoothie; September 7th, 2007 at 04:09 PM. |
|
#5
|
||||
|
||||
|
It sounds like you have the basics. As far as the router, the only change that should be needed on it is changing the WAN IP from DHCP to static. Your VNC access should work as before, but you won't have to worry about the public IP changing anymore.
__________________
cmd /k ipconfig/all [use to start ipconfig from 'Run'] cmd /k ping <some website, like google or yahoo> [use to ping 'www.google.com' from 'Run'] |
![]() |
| Bookmarks |
«
Previous Topic
|
Next Topic
»
| Topic Tools | |
|
|
All times are GMT +1. The time now is 02:19 AM.
[
RSS ]









