Quote:
|
Originally Posted by hokkers999
Quote:
|
Originally Posted by Stuart C
Err, I am Cisco qualified. I know how TCP/IP works, and how NAT works.
My reasoning was that IF netguard needs some sort of activation code sent by NTL (or the original manufacturer), then it may embed the machine's IP in the request for activation. Thus the code would only work on a machine with the same IP as the machine that requested the code.
A lot of software does this.
So, no, being behind a router is NOT irrelevant.
|
Yeh, biggie, so am I. Unless you are running an "enterprise" load then the internal NAT'ed ip is NOT passed through to th e far end. Don't believe me? try running CallServer from NAT to NAT without Enterprise at each end. what's that I hear, oh yeah SILENCE. And yes, I have worked with the R&D guys in Tasman to get that sort of service working (4 years ago if memory serves). Jeez. And besides, how many people do you think are running any sort of Cisco (and I don't count Linksys here) boxes at home?? |
OK, seeing as you have totally misunderstood my point, I will try to explain a little more clearly.
If you are behind a router or firewall with NAT and are running a PC running Windows, type ipconfig, what do you get? The IP address assigned to you by NTL, or the IP assigned to you by the router/firewall? Yep. You get the IP assigned to you by the router/firewall. Windows does not know it's connected to a router. All it knows is that it is connected to a device, and has an IP.
Now, I bought up the Cisco qualification because you appeared to be assuming I do not know how NAT works. I was making the point I do. I also know that the NAT IP is not passed through to the internet connection. I did not do it to start a contest.
Anyway, back to the point of the post. Some software that requires activation uses the IP as part of the ID code for the computer. This, IMO, is a bad idea, but some software does it. When that software requests the IP from Windows, what IP will it get? Yep, the IP assigned by the firewall.
Now, if Netguard does this, it's entirely possible that NTL will not recognise the code as containing an NTL IP. They should recognise it as a member of a private range, but this is NTL we are talking about.
Hopefully, you can now see that the make of router is not relevant to my arguement.
However, the OP has stated he doesn't have a router anyway.