Koozali.org: home of the SME Server

HELP!-IPSEC Freeswan-Windows Clients

Jeff Fentum

HELP!-IPSEC Freeswan-Windows Clients
« on: February 23, 2003, 09:58:10 AM »
I tried to post this question a while back, but no one reponded. Please someone, please help...

I'm currently trying to get 2 SME servers in different "distant"  office locations to provide "LAN" access to each server's network and clients. I've installed the freeswan modules from Darrell May's MyEZServer site. One server is running SME v5.1 (until next month when I can upgrade to 5.5 during a visit), and the other one is using v.5.5. I can make connections via Mac OS-based clients to servers and other Macs based at the other location. But I cannot do the same thing from any of our Winduhs based clients. (Most of my experience with networking computers has been with Macs, and not Windows, so please excuse my ignorance when it comes to all things Redmond.)

My questions are...

Do I have to use a VPN connection from the PC?
On the Mac, all I have to do is click one button in the Chooser, enter the local IP address of the remote server, click "connect", enter my username/password combo and I'm there. The volume I selected to access appears on my desktop, and I have full access to it as if it were a local volume. In Win98 I've tried VPN, Web Folder shares, Network Neighborhood, etc. Nothing works. It seems to me that if both SME servers are creating a bridge between the 2 networks, all the Windows client needs to do is point to the other site's local IP-just like with the Macs- and access the shares. But I'm danged if I can't bumble my way into how to do it from a Win98 client!

Also, does it matter (in the Winduhs sense) that one SME server is running version 5.5 and the other 5.1?

If I'm able to overcome this problem, I will be able to keep the folks at  the company I work for from forcing me to get rid of "that SME thing I've never heard of and get a real server, like WindowsNT."

I would like to better, longer, and spend more time with my family--so please help...

Steve Bush

Re: HELP!-IPSEC Freeswan-Windows Clients
« Reply #1 on: February 23, 2003, 08:03:25 PM »
IPSEC connects the two networks together if setup correctly.
If you can ping the remote server from a windows client,
you should be able to just map a drive to
\\sharename

ie \10.10.1.1\myfiles

Brian Read

Re: HELP!-IPSEC Freeswan-Windows Clients
« Reply #2 on: February 24, 2003, 09:03:59 AM »
You can also "search" for a network computer in Windows Explorer by specifying the IP address.

Cheers

Brian

Michael Smith

Re: HELP!-IPSEC Freeswan-Windows Clients
« Reply #3 on: February 24, 2003, 09:10:39 AM »
Browsing across the VPN is a real pain in the neck, as I can attest, especially w/Win9X clients.  I've not found a good solution yet, but the answer lies in WINS ... if you just need firewalling w/good VPN support you might have a look at IPCop ... I haven't played with one live but it has a way to specify a WINS server for the entire VPN.  You can do this with config files in SME but it ain't painless.

Hayes-Tech

Re: HELP!-IPSEC Freeswan-Windows Clients
« Reply #4 on: February 25, 2003, 01:02:35 AM »
Or us 5.5 for both SME boxes and you can specify an external wins server on each side

Jeff Fentum

Re: HELP!-IPSEC Freeswan-Windows Clients
« Reply #5 on: February 25, 2003, 07:09:48 AM »
First off, thanks to all who responded to my pitiful cries for help.

Steve's tip got me going right away. Now that I think about it, the old Mac OS (v.9) is just as obtuse about connecting to a remote server via its local IP address as Windows is. As far as Windows goes, I thought that I had to "see" the remote server in the network neighborhood before I could access it. Of course, that makes sense, and everything about Windows doesn't.

I appreciate all of the other responses too. Gave me some good insight. I've silenced the pro-Windows critics, for now.