Topic: VPN

[GeraldJ]

I have a client that I will be installing an e-smith server for. They will be using an AT&T athome cable modem connect. I know that works great. I use it at my home. Now I want them to be able to connect with a NT Server  running 4.0 using a ISDN line. I know that the IP address changes each time the connection is broken. However we have a script file that notifies them of the change. So Question is If I have the ip address and the user name and password is setup on the NT server, is it possbile to map a drive on the NT box?

[Gordon Rowell]

GeraldJ wrote:

> I have a client that I will be installing an e-smith server
> for. They will be using an AT&T athome cable modem connect.
> I know that works great. I use it at my home. Now I want them
> to be able to connect with a NT Server  running 4.0 using a
> ISDN line. I know that the IP address changes each time the
> connection is broken. However we have a script file that
> notifies them of the change. So Question is If I have the ip
> address and the user name and password is setup on the NT
> server, is it possbile to map a drive on the NT box?

It should work, but I would not recommend it. Be _very_ concerned
about SMB/Windows filesharing across any public network. Probes on
port 137/138/139 are common-place.

Gordon

[Gordon Rowell]

Gordon Rowell wrote:

> GeraldJ wrote:
>
> > I have a client that I will be installing an e-smith
> > server for. They will be using an AT&T athome cable
> > modem connect. I know that works great. I use it at my
> > home. Now I want them to be able to connect with a NT
> > Server  running 4.0 using a ISDN line. I know that the IP
> > address changes each time the connection is broken.
> > However we have a script file that notifies them of the
> > change. So Question is If I have the ip  address and the
> > user name and password is setup on the NT >server, is it
> > possbile to map a drive on the NT box?
>
> It should work, but I would not recommend it. Be _very_
> concerned about SMB/Windows filesharing across any public
> network. Probes on port 137/138/139 are common-place.

Oops - I think I misread your question and thought you wanted to
connect in the other direction (with the NT box sharing a filesystem).

Let's try again - I'll restate the question to clarify my understanding:

The e-smith server will be on a cable modem with dynamic IP

The NT "client" will be on an ISDN line (static or dynamic IP)

You want to sit at the NT box and map a share to an "ibay" on the
e-smith server

If this is what you mean, then it will not work. We do not share
filesystems on the external interface and would strongly advise against
any attempt to modify the server to allow this.

Gordon

[GeraldJ]

No actually it is the exact reverse. The ISDN is not a static IP although we have a program in place that attempts to maintain a persistent connect.

It will not be necessary to map the drive. A more primative capability would serve. If  a user on the e-smith server were able to establish a ftp connection to the NT server and download a file, as needed and at will that would be sufficent for this situation.

[Gordon Rowell]

GeraldJ wrote:

> No actually it is the exact reverse. The ISDN is not a static
> IP although we have a program in place that attempts to
> maintain a persistent connect.
>
> It will not be necessary to map the drive. A more primative
> capability would serve. If  a user on the e-smith server were
> able to establish a ftp connection to the NT server and
> download a file, as needed and at will that would be sufficent
> for this situation.

OK, then my original response applies. Yes, that should work fine.

Rather than using FTP, I'd suggest installing openssh on the e-smith
server (see www.e-smith.org for details) and an SSH server on the NT
box. You can find references to this from www.freessh.com, notably:

http://marvin.criadvantage.com/caspian/Software/SSHD-NT/default.php

Gordon

[GeraldJ]

Thanks, I'll give it a try.