Ping problems to my SACM (Swindon)

[__spc__]

I've recently set up a personal ftp site using Serv-U on one of my machines (so I can transfer files from work to home). I registered with DYNDNS to give a domain to my dynamic ntl IP (albeit not very dynamic!).

(I have two XP-Home SP2 machines on 192.168.1.10x behind a WRT54G router/AP, CAT5'd into my ntl200 SACM.)

Pinging either my domain name or my IP address from two separate corporate LANS fails; ping from my WLAN (obviously) works.

Are home-user broadband accounts subject to some limit in this respect that prevents their access? Or am I missing something, or is just that my service is screwed at the minute??

The IP address you mention in your post is the one assigned to your PC by your router, not your public IP address supplied by your ISP. It will work anywhere within your private wireless LAN but not from anywhere on the internet - for it to work, you need to discover what IP address your ISP has given you. You can do this by opening the router's config screen in a web browser. The router will have acquired that IP addy, and it's that addy you need to set up with DYNDNS. You then need to do some jiggery pokery on the router to ensure FTP requests that come in to your home network are forwarded by your router to the correct PC, but as I've not yet tried to do that on my own WLAN I'll step aside and let someone else advise you.

[Neil]

I'll move this from the Cable TV forum......

[__spc__]

Originally Posted by Chris T

The IP address you mention in your post is the one assigned to your PC by your router, not your public IP address supplied by your ISP. It will work anywhere within your private wireless LAN but not from anywhere on the internet - for it to work, you need to discover what IP address your ISP has given you. You can do this by opening the router's config screen in a web browser. The router will have acquired that IP addy, and it's that addy you need to set up with DYNDNS. You then need to do some jiggery pokery on the router to ensure FTP requests that come in to your home network are forwarded by your router to the correct PC, but as I've not yet tried to do that on my own WLAN I'll step aside and let someone else advise you.

Thanks Chris, but I am talking about the ntl address 82.10.xxx.xxx and I have port forwarded the ftp of the router to the LAN PC (192.xxx.xxx.xxx) address...