Setting up DynDNS on BSNL WA3002G4

L

LaatSahab

Guide
I've made my BSNL WiFi modem as the PPPoE dialer as I share the Local and Internet access between my desktop,laptop and phone. Now the major services that I intend to use, I've forwarded port for them.



Now below is my DNS Server and DynDNS settings. I'm using the default BSNL DNS server IPs.





Now the trouble is that, I'm not able to access any of my services through other network, i.e. outside my LAN. I'm able to access via LAN only.

If I enter the URL like http://bumpyshah.game-host.org:8080/gui inorder to check out my torrent's status or http://bumpyshah.game-host.org:1987/ to access my shares via HFS on my phone, it doesn't works.

Ironic and strange thing is that HFS is able to check and update for DynDNS updates.





Also if I select the DynDNS domain name and issue open in browser command in HFS, it opens it as http://localhost:1987/ whilst typing the whole domain name and port number and browsing to it gives "Failed to connect" error.

I need it working not only to access my files and shares but also to setup my own web host for my testing purposes and I also want to host game servers which earlier worked flawlessly when my dialer was from Vista and Dynamic DNS update service was provided by no-ip. Please help!
 
After setting the Internal network DNS IP to the modem's IP, things worked out. The issue that remains is that, although uTorrent's Web GUI is accessible but the HFS is not. Have to figure out if its a network issue or HFS issue.
 
now there is a DYNDNS policy with which ... they say ,,, that u wud provide Updates to Hostname Records only and only when ip changes ... not at frequent intervals ... now this is where MOST (actually all of the DSL Routers ) which i had used come's down ...they update at frequent intervals ( this one of ur,s interval is 10 mins ) ... which wud lead to disagreement of Terms of DYNDNS which wud lead to ur HOSTNAME blocked ( disabled by DYNDNS ) ...

so the workway around .... sign in for trial TZO for 30 days ... resign after 30 days to gte another trial ... use TZO with ur Modem and DYNDNS ( for Redundancy ) with ur OS ( by downloading their appropriate OS CLIENT )

for accessing resources ... on the private ... recheck ur settings with Virtual Servers ...
 
just used HFS ... nice ... now can anybody let me know how to get it working as a Windows Service under the Security Context of LOCAL SYSTEM Account ... in working state ... ( as had tried the same ... and was'nt working ... OS used in ma setup ... Win Xp Sp2 under VMware )
 
Yes , I did and I've got it working just fine now. Found out one thing that even if I run the DynDNS client from the modem, still gonna need one running on the desktop for full access. The HFS configured for DynDNS domain takes care of it and now everything is OK.
 
Back
Top