J
Joseph Bruno
I've got two PCs - call them Host (XP Pro) and User (XP Home). They are
connected via Ethernet.
Host has some shared folders (and its Guest account is password-protected).
User can access them over Ethernet and is asked for a password. Everything
works well.
I want to have the same functionality when connecting across the Internet.
So I do the following:
On Host, in the Networking tab of Connection Properties, enable File and
Printer Sharing for Microsoft Networks.
On User , in the Networking tab of Connection Properties, enable Client for
Microsoft Networks.
Temporarily disable Windows Firewall on both computers [to make sure that
this is not a firewall issue].
On Host, dial in to an ISP that gives us a static IP address.
On User, dial in to another ISP.
After this: on User, I can ping Host and get a reasonable response. I can
also set up TCP/IP connections from User to Host.
TRY:
net use \\xxx.xxx.xxx.xxx\test password
where xxx.xxx.xxx.xxx is Host's IP addess (that works with ping) and 'test'
is the name of the shared resource.
RESULT:
Long pause, then error 53.
So - why is it that malicious hackers can connect easily to my open network
shares and I can't? I have presumably missed something obvious but I don't
know what.
connected via Ethernet.
Host has some shared folders (and its Guest account is password-protected).
User can access them over Ethernet and is asked for a password. Everything
works well.
I want to have the same functionality when connecting across the Internet.
So I do the following:
On Host, in the Networking tab of Connection Properties, enable File and
Printer Sharing for Microsoft Networks.
On User , in the Networking tab of Connection Properties, enable Client for
Microsoft Networks.
Temporarily disable Windows Firewall on both computers [to make sure that
this is not a firewall issue].
On Host, dial in to an ISP that gives us a static IP address.
On User, dial in to another ISP.
After this: on User, I can ping Host and get a reasonable response. I can
also set up TCP/IP connections from User to Host.
TRY:
net use \\xxx.xxx.xxx.xxx\test password
where xxx.xxx.xxx.xxx is Host's IP addess (that works with ping) and 'test'
is the name of the shared resource.
RESULT:
Long pause, then error 53.
So - why is it that malicious hackers can connect easily to my open network
shares and I can't? I have presumably missed something obvious but I don't
know what.