Topic: VPN - Unable to view Worgroup

[Olsen]

I have a remote office trying to connect to our SME server through the PPTP vpn so that they can access files on our server.  I setup the Windows XP vpn network connection, and I am able to connect to the server, however, when I go to network places and try to view workgroup computers, It says workgroup is inaccessible.  I verified that we are all in the same workgroup on the computers.  I have set this up successfully in other locations, I dont know why it isnt working this time.  

SME 6.0.1

Can anyone offer suggestions....I am under the bus!

[treyh]

Hey,

This is how I always do it. Instead of using workgroup/computer names, simply browse by ip address. Your server more than likely has a static Lan address.

So lets say your server's ip is 192.168.0.50, you should be able to access it via a unc path.

Go to start-->run-->type in \\192.168.0.50 and then choose ok. Login if needed.

[Olsen]

I have tried that, but all I get is network path not found.  It doesnt make any sense.  I am connected to the pptp, I can see the network traffic on the server manager, but I cannot view any of the workgroup computers or ping any of them either.

I think it might have something to do with the DSL router at that office.  The dsl modem/router names internal machines connected to it as 192.168.1.xxx, meaning it must have an internal address of 192.168.1.1, which is the same as our server from our internal network.  I have had no problems connecting to the server over pptp from a cable modem at my house so it has to be the DSL setup....which does not help me any since there has to be a way to get it setup to work over DSL.  Anyone have an idea?

[treyh]

I have a couple of questions.

1. What dsl modem and router are you using?

2. on your other setup, what cable router are you using?

3. Does the pptp client have any firewalls or anti-virus?

4. the dsl router's ip is probably 192.168.1.1, on the lan machines, is their gateway set to 192.168.1.1 or your sme vpn server?

5. Do the Lan pc's have firewalls or anti-virus?

6. is there anything different between your dsl and cable setup, other than it's 2 different types of service?

[Olsen]

1. What dsl modem and router are you using?
     SBC GLOBAL EWIRE DSL MODEM, it acts as a router
2. on your other setup, what cable router are you using?
     TOSHIBA MODEM / NETGEAR ROUTER

3. Does the pptp client have any firewalls or anti-virus?
     WINDOWS FIREWALL SET TO ALLOW PPTP CONNECTION

4. the dsl router's ip is probably 192.168.1.1, on the lan machines, is their gateway set to 192.168.1.1 or your sme vpn server?
     THE DSL ROUTER IS ACTUALLY 192.168.1.254 AND I WAS ABLE TO DIAL INTO IT, AND WAS LOOKING FOR ANY TYPE OF CONFIGURATION FOR VPN, BUT WAS UNABLE TO FIND ANY.

5. Do the Lan pc's have firewalls or anti-virus?
    YES, FIREWALL AND ANTIVIRUS, BUT IT HASNT AFFECTED THE VPN BEFORE.

6. is there anything different between your dsl and cable setup, other than it's 2 different types of service?
    THERE IS NOTHING DIFFERENT OTHER THAN THE INTERNET SERVICE.

[woyzeck]

Do you have your vpn client connection configured with the sme server ip address as the dns and wins servers?

You will not be able to browse the network with network neighborhood with out wins.

You said that you are not able to ping the machines on the network?  Are you able to ping the sme server?

Woyzeck

[Olsen]

I am using PPTP that is built into SME.  Like I said before, I have been able to utilize this feature through a cable modem but I am unable to get it to work through a dsl modem at this one office.  I can get the VPN to connect, but none of the clients show up in the workgroup.  I am unable to ping any of the clients OR the server.

[treyh]

1. What dsl modem and router are you using?
     SBC GLOBAL EWIRE DSL MODEM, it acts as a router

That is your problem. I have SBC DSL also. I have never used an "Ewire" modem, perhaps they're knew or it's actually a "2wire".

I have a speedstream 5100b, it is an adsl modem and acts as a 1 port router. It holds the dynamic public ip and assigns a lan ip (192.168.1.64) to my pc.

Most of those types of modems, because they also act as a router, have filtering setup on a lot of the ports, including the PPTP port. In your case, it allows you to connect to the PPTP server from the wan side, but then when you're on the lan side, the modem won't route you properly because by default filters those ports to only allow certain access.

Here is the solution:
=====================
If you have a PPPoe account (means you have to authenicate to connect) do this:

Change your network to this

dsl modem (turn off PPPOE), internet port
-->
wan port of router. Turn PPPoe on the router on. (You might have to use a cross over cable between the 2, just depends on the hardware, but of course if the Link Light comes on for wan then you're fine.)
-->
lan ports to pc's. Of course you know that since the router will hold the public ip, you'll have to port forward to the proper lan ip for PPTP

=====================

If you have a static ip do this:

dsl modem (get the static ip), internet port
-->
wan port of router. Set the static ip on the router. (You might have to use a cross over cable between the 2, just depends on the hardware, but of course if the Link Light comes on for wan then you're fine.)
-->
lan ports to pc's. Of course you know that since the router will hold the public ip, you'll have to port forward to the proper lan ip for PPTP

=====================

Another Setup that I can think of, this can also apply for PPPoe or static, but no router. Port forwarding wouldn't be required because the SME Box will need to hold the public ip address.

dsl modem
-->
SME Box (2 nics, does dhcp)
-->
switch
-->
client pc's

=====================

Another Setup that I can think of, this can also apply for PPPoe or static, but with router. Port forwarding would be required since the router is holding the public ip.

dsl modem
-->
router (does dhcp)
-->
SME Server and client pc's

=====================
=====================

Sorry if this was too much data, just wanted to cover as many bases as possible. If none of these situations apply to you, which is quite possible, respond with a network layout (how things connect together) and I will be able to better help you.

[RobRoye]

I actually connect to mine using L2TP VPN from the WinBoxes. I know it's PPTP, but it will not connect using that, it only seems to be happy when it's L2TP.

[Olsen]

treyh,
thanks for the detailed response.  The modem is actually a 2wire modem as you suspected.  I found out that the modem uses PPPoE as a protocol for data transport.  I also found out that PPTP uses the same point to point protocol and it causes grief between the two.  So what I have done is request static ip's from SBC, I am told that we will totally eliminate PPPoE from the picture, thus enabling PPTP.  I hope this works flawlessly cause the CEO is not to happy this isnt working.  

Thanks for your work, I will post back if this static ip setup fixes the problem.

[treyh]

You have a couple other options

1. Get a plain jane dsl modem (like speedstream 5360) and a simple router (d-link or linksys)

2. You might be able to call SBC to see if they can convert your 2wire modem to only be a modem, and then purchase an additional router to use behind the modem.

PPPoe and PPTP should play nice together, the problem is more than likely the modem. A new plain jane modem is under $100, which is a lot cheaper than a STATIC ip from SBC.

[Olsen]

FYI, I upgraded our account with SBC to static IPs.  Once implemented, the VPN worked perfectly.  

I have a feeling the problem was the 2wire modem was dhcp assigning computers on the network 192.168.1.XX

Our SME server uses the same naming, I have a feeling the computers were unable to authenticate because of their ip addresses conflicting with other machines on the network...I may be wrong, but the only thing I care about is that the static IPs work and my problem is solved.

[MSmith]

Your instinct was correct that it was the IP addressing scheme at fault.  You MUST have different addressing schemes for the networks at either end of a VPN, either PPTP or IPSEC.  (Well, that's not  entirely true, but the exceptions are beyond the scope of a simple setup.)

So if you'd simply reset your 2Wire to hand out other addresses you'd've been OK.  Or you could have told your 2Wire to be a bridge and had your SME Server do the PPPoE for you.  But really, the static IP is the best solution.