NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

bobwell's avatar
bobwell
Aspirant
Oct 17, 2017
Solved

Computers in Network Cannot Access Each other NAT after connecting WNR2000v5 to WISP

After connecting the router to a WISP I am unable to communicate between 2 W10 computers on network.  troubleshooting detected a NAT.  A tracing route revealed the first 2 entries were private ISPs.  How do I resolve?  Will changing to WMZ solve the conflict?

 

Thanks, Bob

  • problem has been solved. fyi NAT is Network Address Translation, tracert is cmd to troubleshoot tcp/ip problems- google it

3 Replies

  • > After connecting the router to a WISP [...]

       Connecting how, exactly?  Is the WNR2000v5 the gateway to the ISP, or
    is there some other gizmo involved?

    > [...] I am unable to communicate between 2 W10 computers on network.

       How are these computers connected?  (To what?)  What are their IP
    addresses?  (On a Windows system, open a Command Prompt (CMD.EXE)
    window, and issue an "ipconfig" command.)

    > troubleshooting detected a NAT.

       What does that mean?

    > A tracing route revealed the first 2 entries were private ISPs.

       "traceroute"?  "IP addresses"?  What are these "private ISPs"?  As
    usual, showing actual actions with their actual results (error messages,
    ...) can be more helpful than vague descriptions or interpretations.
    (Copy+paste is your friend.)

    > Will changing to WMZ solve the conflict?

       What does "WMZ" mean to you?  Which "the conflict"?

    • bobwell's avatar
      bobwell
      Aspirant

      problem has been solved. fyi NAT is Network Address Translation, tracert is cmd to troubleshoot tcp/ip problems- google it

      • antinode's avatar
        antinode
        Guru

        > fyi NAT is Network Address Translation,

           Thanks, but I knew what NAT was.  My question was what you were
        talking about, not what NAT meant.

        >  tracert is cmd to troubleshoot tcp/ip problems- google it

           Ok.  "traceroute" for Windows.

        > problem has been solved.

           That's about as informative as the original problem description.