Author Topic: DH Data Recovery Tech Challenge (Read 38150 times)

AJK · « **Reply #120 on:** February 14, 2013, 12:48:38 PM »

Quote from: Name Changed on February 14, 2013, 12:04:31 PM

Ok

I had this issue a few times, I always forgot what was causing it...

I have set up a ftp for accessing files. Port Forwarding was set up, and for some reason it worked perfectly on the local network, but when logging into thru the external IP address I was getting an error in the Browser that network error

Doesn't that clearly indicate a forwarding issue?

Name Changed · « **Reply #121 on:** February 14, 2013, 12:50:27 PM »

Quote from: WiddleAvi on February 14, 2013, 12:44:10 PM

Permissions issue

Nope

Quote from: AJK on February 14, 2013, 12:48:38 PM

Doesn't that clearly indicate a forwarding issue?

Point is is wasn't a fwding issue

real-brisker · « **Reply #122 on:** February 14, 2013, 12:52:55 PM »

Firewall? Filter?

Centurion · « **Reply #123 on:** February 14, 2013, 12:54:36 PM »

specific port not designated/opened in lan envirment

BAHayman · « **Reply #124 on:** February 14, 2013, 12:57:35 PM »

ipv6? isp?

Name Changed · « **Reply #125 on:** February 14, 2013, 01:00:42 PM »

Quote from: BAHayman on February 14, 2013, 12:57:35 PM

ipv6? isp?

I'm trying to pinpoint the exact issue, you are close

Explain more

BAHayman · « **Reply #126 on:** February 14, 2013, 01:09:44 PM »

Quote from: Name Changed on February 14, 2013, 01:00:42 PM

I'm trying to pinpoint the exact issue, you are close

Explain more

Isp has the port blocked.
Or your connecting over ipv6 and either the router or ftp server cannot handle an ipv6 address.

Name Changed · « **Reply #127 on:** February 14, 2013, 01:15:16 PM »

Quote from: BAHayman on February 14, 2013, 01:09:44 PM

Isp has the port blocked.
Or your connecting over ipv6 and either the router or ftp server cannot handle an ipv6 address.

Neither

DH Data Recovery · « **Reply #128 on:** February 14, 2013, 01:25:08 PM »

I would go with 1) Check firewall - very common issue.
2) are you connecting to the ftp using local ip address or public address? What ftp server are you running?

Name Changed · « **Reply #129 on:** February 14, 2013, 01:26:59 PM »

Quote from: DH Data Recovery on February 14, 2013, 01:25:08 PM

I would go with 1) Check firewall - very common issue.
2) are you connecting to the ftp using local ip address or public address? What ftp server are you running?

Wasn't firewall issue.

Connecting from local address.

DH Data Recovery · « **Reply #130 on:** February 14, 2013, 01:29:39 PM »

Opened the correct port?

Name Changed · « **Reply #131 on:** February 14, 2013, 01:32:29 PM »

Quote from: DH Data Recovery on February 14, 2013, 01:29:39 PM

Opened the correct port?

Yup.

BAHayman · « **Reply #132 on:** February 14, 2013, 01:33:21 PM »

Forwarded to the port to the correct local IP Address?

Name Changed · « **Reply #133 on:** February 14, 2013, 01:34:08 PM »

Quote from: BAHayman on February 14, 2013, 01:33:21 PM

Forwarded to the port to the correct local IP Address?

Yup

DH Data Recovery · « **Reply #134 on:** February 14, 2013, 01:39:12 PM »

Whats the exact message?

yuneeq · « **Reply #135 on:** February 14, 2013, 01:45:15 PM »

Your LAN was connected to the internet?

Name Changed · « **Reply #136 on:** February 14, 2013, 01:47:41 PM »

Quote from: yuneeq on February 14, 2013, 01:45:15 PM

Your LAN was connected to the internet?

Yes

BAHayman · « **Reply #137 on:** February 14, 2013, 01:51:11 PM »

Firewall already had a port forwarding rule for that port? Router/Firewall/Modem has a service running on that port?

Name Changed · « **Reply #138 on:** February 14, 2013, 01:55:40 PM »

Quote from: DH Data Recovery on February 14, 2013, 01:39:12 PM

Whats the exact message?

Oops! Google Chrome could not connect to XX.XXX.XX.XXX

or with IE
Internet Explorer cannot display the webpage

Name Changed · « **Reply #139 on:** February 14, 2013, 01:57:16 PM »

Quote from: BAHayman on February 14, 2013, 01:51:11 PM

Firewall already had a port forwarding rule for that port? Router/Firewall/Modem has a service running on that port?

I dont think it was a firewall issue at all