Koozali.org: home of the SME Server

[7RC2] PPTP connects OK, can't see workgroup or shares

Offline dtech

  • ***
  • 70
  • +0/-0
[7RC2] PPTP connects OK, can't see workgroup or shares
« on: May 16, 2006, 12:23:19 AM »
Here's the setup; the SME server has two ethernet cards, one connects directly to the DSL modem and the other connects to a switch that the workstations are connected to. From a remote location I am able to set up PPTP on Windows XPSP2, and I can connect and authenticate succesfully on the SME server. The problem is that I can't access any remote network resources; no ibays, no server-manager, etc.

When I set up the SME server Remote Access panel, all I did was allow one connection, and modified the user to be able to have VPN access in the User panel. I did not do any port forwarding (as I've seen mentioned in the forums), because the SME server is internet facing; there is no router between it and the internet.

When I set up the remote XP box, I just went through the wizard and made no modifications to the defaults. Again, I can connect, I just can't access any resources.

If I try to add a network drive, for example, I try to browse for a location and the workgroup on the server's network never comes up. I get my home workgroup and resources.

For what it's worth, both networks use 192.168.0.XXX for IPs, and the SME server's internal IP is 192.168.0.1 which is the same as the gateway router on the remote network.

Thanks in advance,

-Pete

Offline dtech

  • ***
  • 70
  • +0/-0
[7RC2] PPTP connects OK, can't see workgroup or shares
« Reply #1 on: May 24, 2006, 12:19:22 AM »
OK, answering my own post after hammering away at this for a few days. I have found what I need to do to make this work, although now I have some other questions.

I was logging in to the SME7RC2 pptp server from the home office network. The home office box has XPSP2 on it. I go through the little 'Create a new connection' wizard on XP, enter my SME username and password (username is the same on both networks, password is different), and am able to connect to the SME server. But, I was not able to see or connect to any network resources. So, I try to connect a network drive manually by typing in the name of the share using the \\server\share convention, no dice. I get an error that says something about bad password or username, so I change the password on my home box to match the password on the SME server and bingo, now the shares are available if I do the manual entry thing.

So now I know that even though I connect to the SME server using the username/password combo of my account on the SME network, Windows will use my local username/password combo to attach to shared resources.  I also know that there is the option to connect to a network drive using another name/password combo, but this doesn't seem to work in this case. The only way I can get this to work is to change the password of my office XP box to match that of my user account on the SME network.

Does anyone else have any insight here, or is this obvious to everyone but me? This is looking like it would be a good HOWTO.

Thanks,

-Pete

Offline dtech

  • ***
  • 70
  • +0/-0
[7RC2] PPTP connects OK, can't see workgroup or shares
« Reply #2 on: May 24, 2006, 12:33:40 AM »
OK, I guess Windows had to think about things for a little while, because now I'm connecting to network shares by using the 'Connect using a different user name' function that can be selected when doing the 'Map Network Drive'. This didn't work at all the first few times I tried it.

Carry on,

-Pete

xjjk16x

[7RC2] PPTP connects OK, can't see workgroup or shares
« Reply #3 on: May 24, 2006, 06:32:57 PM »
"both networks use 192.168.0.XXX"

That will be a problem on vpn networks...

make sure each network is on a different subnet.

i.e   192.168.0.xxx   connects to any other private network other than a similar 192.168.0.xxx

use 192.168.1.xxx
      192.168.3.xxx

but do not use 192.168.0.xxx for both

Also connecting via unc over a vpn takes some setup too.

try using a wins server.

or you can always use \\192.168.0.222 etc