I thought this would be easy, but maybe I'm missing something obvious.

I want to be able to connect to a Win2000 PC behind an ADSL router. The PC
has been setup to share correctly . I can connect to it from the LAN. The
firewall on the PC is off.

In my ADSL router I have set up port forwarding on TCP 137,138,139 and 445,
and
UDP 137,138,139 and 445 to go to the PC on the internal network's ip address
eg. 192.168.0.20

I have my PCs members of the same Workgroup.

From the computer on the outside of my firewall, I go into My Network
Places, and choose Add Network place and type:

\\81.34.56.123\sharename (as an example)

And try to connect.

Nothing happens. I get "the network path cannot be found"

Am I being monumentally stupid and missing some obvious step, or does
Windows File Sharing end up being more complicated than something like HTTP,
FTP, SSH, or POP where I simply port forward and that just solves the
problem.

Any ideas appreciated.

Some ISPs do not allow this type of traffic. You might try configuring a
VPN and connecting that way. Use port 1701 for L2TP or port 1723 for PPTP.
Another open would be install teminal servers in remote administration mode
and connect that way. Use port 3389 for that.

"Bonge Boo!" <(E-Mail Removed)> wrote in message
news:BC52E133.6024C%(E-Mail Removed)...
> I thought this would be easy, but maybe I'm missing something obvious.
>
> I want to be able to connect to a Win2000 PC behind an ADSL router. The PC
> has been setup to share correctly . I can connect to it from the LAN. The
> firewall on the PC is off.
>
> In my ADSL router I have set up port forwarding on TCP 137,138,139 and
445,
> and
> UDP 137,138,139 and 445 to go to the PC on the internal network's ip
address
> eg. 192.168.0.20
>
> I have my PCs members of the same Workgroup.
>
> From the computer on the outside of my firewall, I go into My Network
> Places, and choose Add Network place and type:
>
> \\81.34.56.123\sharename (as an example)
>
> And try to connect.
>
> Nothing happens. I get "the network path cannot be found"
>
> Am I being monumentally stupid and missing some obvious step, or does
> Windows File Sharing end up being more complicated than something like
HTTP,
> FTP, SSH, or POP where I simply port forward and that just solves the
> problem.
>
> Any ideas appreciated.
>
>

On 14/2/04 4:35, in article (E-Mail Removed), "Rob
Elder, MVP-Networking" <(E-Mail Removed)> wrote:

> Some ISPs do not allow this type of traffic. You might try configuring a
> VPN and connecting that way. Use port 1701 for L2TP or port 1723 for PPTP.
> Another open would be install teminal servers in remote administration mode
> and connect that way. Use port 3389 for that.

Thanks for that, but a VPN is not an option sadly. From my description of
what I have done, have I set up my end correctly for a simple WAN
connection?

Anything I've missed?

>> I thought this would be easy, but maybe I'm missing something obvious.
>>
>> I want to be able to connect to a Win2000 PC behind an ADSL router. The PC
>> has been setup to share correctly . I can connect to it from the LAN. The
>> firewall on the PC is off.
>>
>> In my ADSL router I have set up port forwarding on TCP 137,138,139 and 445,
>> and
>> UDP 137,138,139 and 445 to go to the PC on the internal network's ip address
>> eg. 192.168.0.20
>>
>> I have my PCs members of the same Workgroup.
>>
>> From the computer on the outside of my firewall, I go into My Network
>> Places, and choose Add Network place and type:
>>
>> \\81.34.56.123\sharename (as an example)
>>
>> And try to connect.
>>
>> Nothing happens. I get "the network path cannot be found"
>>
>> Am I being monumentally stupid and missing some obvious step, or does
>> Windows File Sharing end up being more complicated than something like HTTP,
>> FTP, SSH, or POP where I simply port forward and that just solves the
>> problem.
>>
>> Any ideas appreciated.
>>
>>
>
>