remote access via No-Ip.com

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,
I've registered an account and name with No-Ip and have pinged it, so know
it's there. What further measures do I need to do in Xp to access the PC from
another. Been reading around Microsft, but it only seems to dwell on their
own system, not using a dynamic IP updater like No-Ip. I think I need to
reconfigure Windows Firewall and Zone Alarm for Port 3389?

Any advice welcome.
Peter
 
peterpann said:
Hello,
I've registered an account and name with No-Ip and have pinged it, so
know it's there. What further measures do I need to do in Xp to
access the PC from another. Been reading around Microsft, but it only
seems to dwell on their own system, not using a dynamic IP updater
like No-Ip. I think I need to reconfigure Windows Firewall and Zone
Alarm for Port 3389?

Yes, but you also need to make sure your no-ip account gets updated with the
correct public IP, via something like DirectUpdate (google it) which runs as
a service.
 
Actually, the No-IP.com client runs as a service on an XP machine...or can be setup that way...and
the update time configured... Look in "Options" when the client is opened on the desktop..

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
 
Sooner said:
Actually, the No-IP.com client runs as a service on an XP
machine...or can be setup that way...and the update time
configured... Look in "Options" when the client is opened on the
desktop..

k; thanks - I've always used dyndns.org and direct update. same thingy. :)
"Lanwench [MVP - Exchange]"
Yes, but you also need to make sure your no-ip account gets updated
with the correct public IP, via something like DirectUpdate (google
it) which runs as a service.
 
Sooner, Ta for you reply. Not sure about what you mean though. I have the
Dynamic Update Client (DUC) installed, do I need to reconfigure that in any
way? I'm new to this, so I was thinking I connect to Broadband, launch DUC
and then it should be accessable by any other PC.
How physically do I access from the other PC? What address do I type, or do
I log into No-Ip and get it from there. Sorry to sound a bit thick!!
Cheers,
Peter

Lanwench said:
Sooner said:
Actually, the No-IP.com client runs as a service on an XP
machine...or can be setup that way...and the update time
configured... Look in "Options" when the client is opened on the
desktop..

k; thanks - I've always used dyndns.org and direct update. same thingy. :)
"Lanwench [MVP - Exchange]"
peterpann wrote:
Hello,
I've registered an account and name with No-Ip and have pinged it,
so know it's there. What further measures do I need to do in Xp to
access the PC from another. Been reading around Microsft, but it
only seems to dwell on their own system, not using a dynamic IP
updater like No-Ip. I think I need to reconfigure Windows Firewall
and Zone Alarm for Port 3389?

Yes, but you also need to make sure your no-ip account gets updated
with the correct public IP, via something like DirectUpdate (google
it) which runs as a service.

Any advice welcome.
Peter
 
That's basically the way it works, ie. start up the DUC and the client should automatically connect
to the No-IP servers and map your current IP to your chosen fully qualified domain name. What I was
alluding to is if you go into the "Options" windows you can configure for "auto startup when you log
in", as a "service", etc...etc...etc... Personally I have mine set up as a "service" so the DUC
starts as soon as the PC starts up. That way no matter what account I use to log onto my PC the DUC
is always started and running once the PC boots up...

You can also change the update period in this "Options" windows. I have mine set to 10 minutes, but
the default is probably sufficient. All of the rest of my settings are the defaults.

To call from a remote location simply use the fully qualified domain name you choose when you
established your account with No-IP.com... This presumes you have port forwarding setup through your
router and that Remote Desktop is enabled on the PC you want to connect to.

Note that you can *NOT* use the fully qualified domain name to test this over a local LAN from
another local PC. In that case use the private LAN IP or the name of the PC... See the "Test on the
local LAN" section of the page I pointed you to earlier...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
 
Hey, Thanks for your good advice. I think I should've cracked it, just need
to test it from another PC. Can't use work's as it's on anetwrok and stuff
like No-Ip is blocked anyway.
Thanks again,
Peter
 
Back
Top