Koozali.org: home of the SME Server

trouble with vpn to internal domain

janhein

trouble with vpn to internal domain
« on: December 03, 2004, 06:58:26 PM »
Hello,
We have the next problem.

We have sme 6.0.1 installed and works as a server/gateway. Behind this we have an W2000 domain controller.
We make an vpn to the sme and then want to login to the domain of the w2000 server.
The vpn to the sme is no problem, but we can't get login on the w2000 domain.
We can ping to the internal network with the ip number and with the name of the internal computers.
So we think that the dns is working well.

The settings of the clients (all XP pro) who makes the vpn connection are ok, because we set the dns to the ip of the w2000 server, and the wins also to the w2000 server.

When we type //192.168.0.... we can see the shares of the w2000 server. But when we do this with the hostname we can't see anything and get the message the that the hostname can not be found.

Can somebody help us?
Is there some settings in the sme that we forget?

By the way we had sme 5.6 running and we had no problems. Is there a difference in the settings on 5.6 and 6.0.1?

Please help us  :idea:

bobk

trouble with vpn to internal domain
« Reply #1 on: December 03, 2004, 10:45:15 PM »
Here are couple things you can try:

1. Give the W2K server a fixed IP address outside the DHCP range and enter that Host Name and IP in the "Hostnames and addresses" panel on the SME Server.

2. Download and install the "Advanced workgroup" SM Panel ver 0.3-4. http://www.ibiblio.org/pub/Linux/distributions/smeserver/contribs/jprice/beta/e-smith-advworkgroup/
Then use it to configure the W2K server as the WINS server for the domain.

ryan

trouble with vpn to internal domain
« Reply #2 on: December 05, 2004, 07:07:45 AM »
Bob,

Give this a try,

Create a new VPN connection in XP/2k...make it available for all users.  

Notice when logging in on your XP pptp computer, XPoffers a check box that allows you to establish your VPN before logging into Windows.  If your VPN/DNS is working, your client will log to VPN first, and then the domain second as if they where on the local lan (with pptp they are on the local lan).  

I have several clients that operate in this way.

good luck,

ryan

janhein

Did not help
« Reply #3 on: December 09, 2004, 07:37:56 PM »
Quote from: "bobk"
Here are couple things you can try:

1. Give the W2K server a fixed IP address outside the DHCP range and enter that Host Name and IP in the "Hostnames and addresses" panel on the SME Server.

2. Download and install the "Advanced workgroup" SM Panel ver 0.3-4. http://www.ibiblio.org/pub/Linux/distributions/smeserver/contribs/jprice/beta/e-smith-advworkgroup/
Then use it to configure the W2K server as the WINS server for the domain.


We tryed your suggestion nr.1, but it didn't help.
The w2k server has an fixed ip outside the dhcp range. In "hostnames and adresses" we ad the hostname and ip of the w2k server and set it to local. Do we have to enter more ip numbers? The name is then "servername.domain.local" Is this ok?

Jan Hein

janhein

trouble with vpn to internal domain
« Reply #4 on: December 09, 2004, 07:40:06 PM »
Quote from: "ryan"
Bob,

Give this a try,

Create a new VPN connection in XP/2k...make it available for all users.  

Notice when logging in on your XP pptp computer, XPoffers a check box that allows you to establish your VPN before logging into Windows.  If your VPN/DNS is working, your client will log to VPN first, and then the domain second as if they where on the local lan (with pptp they are on the local lan).  

I have several clients that operate in this way.

good luck,

ryan


This is the way we already made the vpn connection and want to login to the domain.
The vpn connection is ok. But when we want to join the domain, everything stops. It also made us sometimes have to reboot the client computer.

Jan Hein

ryan

trouble with vpn to internal domain
« Reply #5 on: December 10, 2004, 06:33:38 PM »
Does your statement "join a domain" means you are attempting to make a workgroup PC a domain member by joining a domain over a PPTP connection? I have never tried this.  

It will work if your have a site to site (router to router or server to server) IPSEC VPN tunnel (THIS IS NOT PPTP VPN)and all routing/DNS/AD sites & subnets are configured correctly.  

ryan

janhein

trouble with vpn to internal domain
« Reply #6 on: December 13, 2004, 08:37:14 AM »
Quote from: "ryan"
Does your statement "join a domain" means you are attempting to make a workgroup PC a domain member by joining a domain over a PPTP connection? I have never tried this.


Yes, this is what we want to do. When we had version 5.1.6 this worked great. We have never had any problem.
Now we have upgraded to version 6.0.1 we can make an vpn to the sme, but when we want to join the domain everyting does not work.
The difference I see between the two versions is, that in version 5.1.6 there are no network settings in "local networks".
In version 6.0.1 this is automatic set to network 10.0.0.0 and subnetmask 255.0.0.0 .(the internal lan)
Is this may be an problem?
Is it possible that there are some DNS problems?

Jan Hein