Re: How to better secure my wireless transmissions on my home WLAN? VPN?



"__spc__" <spamtime@xxxxxxxxxxxx> wrote in news:1129560420.782959.166180
@z14g2000cwz.googlegroups.com:

> Thanks for this Duane - the links were useful, and I read them in
> conjunction with the WRT54G user manual which helped greatly.
>
> So, for port forwarding, do I need a static IP address from my ISP - so
> that I know which address to use when accessing the service externally?
>
>

The static IP is for whatever IP/machine on your LAN the traffic for the
inbound port the application on the machine needs open to be forwared to
that IP. Set the NIC on the computer through the Windows O/S to use one
of the router's static IP(s) and not an IP that can be issued through the
DHCP of the router. If the DHCP IP(s) that can be issued are 5 as an
example, then the DHCP IP(s) the router can issue are from 192.168.1.100
through 192.168.1.105. 192.168.1.106 and out are static IP(s) on the
router. The D in DHCP means Dynamic.

So the NIC on the card would be set to *Use the following* IP(s)

IP = 192.168.1.106
Subnet = 255.255.255.0
Gateway = 192.168.1.1 or is know as the router's Device IP.

Use the following DNS IP(s) --- which are the ISP(s) IP(s)

DNS1 = XXX.XXX.XXX.XXX
DNS2 = XXX.XXX.XXX.XXX

You'll find the ISP's DNS IP(S) on one of the router's Admin Screens,
which you'll also see the ISP's IP that has been issued at the time to
the router. The DNS IP(s) are static IP(s) that you'll enter for DNS1 and
DNS2.

If you port forwarded to a machine that uses a DHCP IP, the IP could
change for the machine to something else. But using a static IP like
192.168.1.106 in the above example, the IP for the machine on the LAN
that is being port forwarded to will not change its IP and port
forwarding will always point to 192.168.1.106. because it's static.

That's what is meant by using a static IP on the router is make the
computer's NIC wire or wireless use one of the router's static IP(s) so
that the computer keeps the same IP and it never changes.

Duane :)
.



Relevant Pages

  • Re: Testing environment question
    ... For your domain members to function properly they must use the local DNS server. ... Turn off the DHCP function on the router. ... You can set up DHCP on the DC or you can just configure the machines manually to use the router for default gateway but use the DC for DNS. ...
    (microsoft.public.windows.server.general)
  • Re: Networking problems (again) tough one
    ... The problem *only* occurs on my Linux machines. ... DNS numbers, ... all systems start working again whether setup manually or with DHCP. ... If theu are shoing good, and yet things dont work, you may have a misconfigured router. ...
    (comp.os.linux.setup)
  • Re: DNS Problem??
    ... In the DHCP field at the router, ... > DNS but it adds the 'public' side DNS automatically. ... Do you have another SERVER class machine with the clients? ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP from Router to SBS Server
    ... If you are using a single NIC configuration you can use the DHCP on the router *IF* your router supports forwarding DNS to a computer on the LAN side. ...
    (microsoft.public.windows.server.sbs)
  • Re: Testing environment question
    ... For your domain members to function properly they must use the local DNS server. ... You can set up DHCP on the DC or you can just configure the machines manually to use the router for default gateway but use the DC for DNS. ...
    (microsoft.public.windows.server.general)

Loading