wireless router - Static IP isn't accessible outside of the home network

08
2014-07
  • Dmitry

    I have Windows 2012 server with HTTP server enabled through the firewall. I mapped my static IP to my local IIS using the router's port forwarding. Everything worked fine for awhile.

    All of a sudden I found that my static IP only gets resolved in my home network (I'm using noip.com DUC to emulate it, but it's pretty stable). Haven't seen it changing in last 6 months) even though it used to work fine in any network a few weeks back.

    How do I fix it and what is the problem?


    Update:

    tracert

     1     1 ms     2 ms     1 ms  [Kind_of_My_IP].ntlworld.ie [My_Public_IP]
    

    pathping

    Tracing route to [Kind_of_My_IP].ntlworld.ie [My_IP]
    over a maximum of 30 hops:
      0  My_PC_Name [192.168.0.**]
      1  [Kind_of_My_IP].ntlworld.ie [My_IP]
    
    Computing statistics for 25 seconds...
                Source to Here   This Node/Link
    Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
      0                                           My_PC_Name [My_IP]
                                    0/ 100 =  0%   |
      1    3ms     0/ 100 =  0%     0/ 100 =  0%  [Kind_of_My_IP].ntlworld.ie [My_IP]
    
    Trace complete.
    

    pathping to Google

    Tracing route to google.com [74.125.24.100]
    over a maximum of 30 hops:
    
      1     1 ms     1 ms     4 ms  192.168.*.*
      2    11 ms     8 ms     8 ms  [Kind of my IP].ntlworld.ie [My_IP]
      3     7 ms     7 ms     9 ms  188-141-126-1.dynamic.upc.ie [188.141.126.1]
      4    53 ms     8 ms     9 ms  84.116.238.50
      5     9 ms     8 ms     8 ms  213.46.165.18
      6    11 ms   104 ms     8 ms  209.85.252.198
      7    13 ms    18 ms    10 ms  72.14.235.141
      8     *        *        *     Request timed out.
      9    10 ms     8 ms     9 ms  de-in-f100.1e100.net [74.125.24.100]
    

    ipconfig /all

    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : PC_NAME
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
    
    Wireless LAN adapter Wireless Network Connection 2:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
       Physical Address. . . . . . . . . : C4-85-08-43-86-37
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Ethernet adapter Bluetooth Network Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
       Physical Address. . . . . . . . . : C4-85-08-43-86-3A
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Wireless LAN adapter Wireless Network Connection:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6235
       Physical Address. . . . . . . . . : C4-85-08-43-86-36
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::7cc9:627d:a372:d014%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.10(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 14 June 2014 13:27:28
       Lease Expires . . . . . . . . . . : 24 June 2014 17:52:10
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 314869000
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-3E-44-A1-E8-03-9A-DD-05-36
    
       DNS Servers . . . . . . . . . . . : fe80::1%12
                                           89.101.160.4
                                           89.101.160.5
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter Local Area Connection:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : E8-03-9A-DD-05-36
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{09812F18-3847-40F7-8A73-8B3142155535}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{3C02EA27-66E8-483B-B613-9DDF25B777C2}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{25320524-8E25-4DAC-AF6F-B9E4C76F6BF8}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter Local Area Connection* 11:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:202a:921:a69b:85e7(Prefe
    rred)
       Link-local IPv6 Address . . . . . : fe80::202a:921:a69b:85e7%16(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled
    
    Tunnel adapter isatap.{B8761C80-6080-4C2B-B307-2472A3B71C3C}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    

    First 2 octets: 89.100.

  • Answers
  • harrymc

    I assume that your static IP is IPv4, but I see that you have IPv6 on, which may cause a confusion.

    Try to turn IPv4 off in the PC and the router.

    As far as the PC is concerned, here are some useful resources.

    How To Disable IPv6 On Windows 7 (article 1)

    In Control Panel -> Network and Sharing Center, click the connection, then Properties, uncheck "Internet protocol version 6" and OK.

    How To Disable IPv6 In Windows 7 (article 2)

    To make the above change permanent, use regedit to navigate to :
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TCPIP6\Parameters.

    Click Parameters in the left sidebar, then right-click on the right and choose:
    New > DWORD (32-bit). Name it DisabledComponents and set its value to 0.

    Reboot to check if IPv6 is truly turned off.

    Before doing registry work, ensure your backups are done and create a system restore point.

  • Codezilla

    Is it possible that your internal ip address got renewed from the dhcp server on your router to a new ip causing any port forwarding you've done to point to the wrong ip address in your internal network and also causing the domain from noip to point to your static ip but not the correct ip on your internal network?

    Sounds highly probable that that is the issue.


  • Related Question

    osx - Intranet, no Internet after switch to static IP on OS X
  • hewhocutsdown

    I have a Linksys WRT54GS and have two machines on my network connecting wirelessly. DHCP is enabled, and is granting IP addresses in the .100-120 range. The one machine is a laptop running Ubuntu 10.04 and it is working via DHCP, IP address .103.

    The second machine, OS X 10.4, I set to a static IP in order to allow port forwarding from the router, as per these instructions: http://portforward.com/networking/static-Mac10.4.htm. It's grabbing an IP address outside of the DHCP range; .13.

    Since I did so, the Mac can see the local network, and I can access the router config from it, but all traffic outside of my LAN is blocked for that machine. I see no settings indicating any sort of filter or rules that would block web access.

    Where did I go wrong?


  • Related Answers
  • Spiff

    When manually configuring the 10.4 machine, did you enter the subnet mask and the router's address correctly?

    When testing off-network connectivity, did you try connecting to things by IP address or just by name? Because maybe you forgot to enter a valid DNS server address on your 10.4 client, and since it's not getting that information via DHCP anymore, it doesn't know who to ask when it needs to look up the IP address for a given hostname.

  • NReilingh

    Are you trying to use the "DHCP with Manual IP" setup available in OS X's Network system preferences? I personally have never gotten that to work properly. Make sure you're configuring TCP/IP "Manually" and copying all of the addresses (Including DNS) from what would be distributed by DHCP except for the IP address.

    Something else I would recommend, not as a fix but as an advanced alternative, would be to set up your router to do some static DHCP: distribute a predetermined IP address to the 10.4 machine based on the MAC address of its ethernet interface. You probably can't do this with the stock firmware on that router, but that router is well known in the community to be a good candidate for alternative firmware such as DD-WRT. I personally have had great success with Tomato, which is very lightweight and easy to use, while drastically expanding on the limited feature set of Linksys stock firmware.