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??