G
Guest
Hello all,
I'm new here so feel free to let me know if I make a mistake or doesn't
provide enough detail...
I got a site-to-site VPN working with a D-link DFL-1100 VPN Firewall on one
end (lets call it Site-A), a DFL-700 on another (site-B?). The VPN worked
like a charm, I can ping any terminals in either of those 2 sites. I can even
establish Telnet/SSH connection between terminals on both sites and also to
SCO Unix server on site-A. On each site, I got around 10 PC's with Windows XP
on them. XP Home to be exact and all of them can communicate using telnet to
the server.
Now, I did assign all the PC in the site to the same workgroup and enable
file/printer-sharing, and any terminals can share stuff between each other on
the same site.... or should I say the same LAN...
However... they cannot share through VPN to any other terminals on the other
LAN site. With me so far? Apparently Microsoft Windows Network can only
recognize workgroups on the LAN, not across VPN (although I thought the
purpose of VPN is to "virtualize a private network"?), so I cannot enable
file-sharing across the VPN... It pings... its connected alright.
I even tried to network drive a folder in a terminal in site-B from a
terminal in site-A. I enter the ip address, and the folder name, but nope...
didn't work. (in the background I got a command prompt that pings the ip
address and i'm having replies).
So the question is, is it possible at all to share-files between 2 LAN-sites
connected via VPN?
If yes, how? if not, I'd probably just going to setup an FTP server in 1 of
the site for people to access to, although its so tedious to login/logout
using some FTP-client to work on a file, and then uploading them back. Not to
mention the possibility that 2 or more people access the files in the same
time. With file-sharing its easier to work with file-permission and stuff...
I looked up Windows 2003 server white pages for setting up VPN (coz I'm
assuming VPN connectivity with a Microsoft product "should" be able to
connect to a Microsoft Network. dumb logic i know), and they does require
opening certain ports (45, 5000, etc) for Windows Network but there's a
wizard to take care of that automatically and the total is like 120 ports....
Phew... sorry if the problem been posted somewhere else, but thanks for the
replies!!!!
Dave
I'm new here so feel free to let me know if I make a mistake or doesn't
provide enough detail...
I got a site-to-site VPN working with a D-link DFL-1100 VPN Firewall on one
end (lets call it Site-A), a DFL-700 on another (site-B?). The VPN worked
like a charm, I can ping any terminals in either of those 2 sites. I can even
establish Telnet/SSH connection between terminals on both sites and also to
SCO Unix server on site-A. On each site, I got around 10 PC's with Windows XP
on them. XP Home to be exact and all of them can communicate using telnet to
the server.
Now, I did assign all the PC in the site to the same workgroup and enable
file/printer-sharing, and any terminals can share stuff between each other on
the same site.... or should I say the same LAN...
However... they cannot share through VPN to any other terminals on the other
LAN site. With me so far? Apparently Microsoft Windows Network can only
recognize workgroups on the LAN, not across VPN (although I thought the
purpose of VPN is to "virtualize a private network"?), so I cannot enable
file-sharing across the VPN... It pings... its connected alright.
I even tried to network drive a folder in a terminal in site-B from a
terminal in site-A. I enter the ip address, and the folder name, but nope...
didn't work. (in the background I got a command prompt that pings the ip
address and i'm having replies).
So the question is, is it possible at all to share-files between 2 LAN-sites
connected via VPN?
If yes, how? if not, I'd probably just going to setup an FTP server in 1 of
the site for people to access to, although its so tedious to login/logout
using some FTP-client to work on a file, and then uploading them back. Not to
mention the possibility that 2 or more people access the files in the same
time. With file-sharing its easier to work with file-permission and stuff...
I looked up Windows 2003 server white pages for setting up VPN (coz I'm
assuming VPN connectivity with a Microsoft product "should" be able to
connect to a Microsoft Network. dumb logic i know), and they does require
opening certain ports (45, 5000, etc) for Windows Network but there's a
wizard to take care of that automatically and the total is like 120 ports....
Phew... sorry if the problem been posted somewhere else, but thanks for the
replies!!!!
Dave