local participation option

[Cliff Dungey]

After I registered Wingate VPN the local participation option is no longer there.

Please tell me what it is set to by default when I no longer have the option?.

Thanks.
Cliff.

[MattP]

Hi Cliff,

You won't have the local network option if you've purchased a single user license, but you should be able to select local machine only or no local access. What license did you purchase?

[Cliff Dungey]

Hi Matt,
I sent you a screen snapshot in you email.

Thanks.
Cliff.

[MattP]

Righto, got them thanks.

The way it works is you don't get to choose your local participation level if you've got a single user license and you're the joiner. If you were to choose no local participation then there would be no point in joining the VPN because you wouldn't be able to do anything and no-one at the remote end (the host side) would be able to access you either.

If you are hosting the VPN then we give you the option to choose no local participation or local machine only.

[Cliff Dungey]

Ok.
This is the issue.
I have 2 managers in a meeting room offsite using there laptops with wireless access.

Same os, install, config file, different usernames and same access point in the motel.

When the first user connects all is well, when the second user connects I get local conflict under published routes on the last laptop to connect to the server.

If I switch one of the laptops to a different access point then all is well.

It looks like the software will not allow two connections at the same time from the same access point.

I'm running it hear at my test bench, one wireless and one on LAN and I'm not able to have the two connections at the same time also, I get the same error.
Is this an issue in Wingate?.

Thanks.
Cliff.

[Cliff Dungey]

Hi Matt...
All is well....
I changed local participation on the server to Local Machine Only and that resolved the issue.

I hate the learning curve...

Thanks.
Cliff.

[MattP]

I've just set it up here using your license for the single user VPN and it worked well. We had two machines connecting out through a WinGate server (we don't have a wireless access point but that shouldn't matter), each machine was running WinGate VPN with a single user license. Both machines were able to join the VPN and successfully browse files on the host server at the same time, so it should work for you.

In saying that, the screen shot that you sent me showed that the machines were exporting routes for their local subnet, which they shouldn't be doing if they have a single user VPN license, can you check this please?

[Cliff Dungey]

The first laptop has the single user VPN license.
The second laptop had the trial license.
The trial license Local Participation is set to Local Machine Only.

This tells me that the two of them are set to Local Machine Only.

I was playing with it last night and all looked ok but when I turned it on today I get the local conflict under published routes error.

Thanks.
Cliff.

[MattP]

And if you look at the published routes on each machine do you see a route for the subnet that they're on? ie a route for 192.168.0.0 (or whatever their subnet is, with the last octet being a zero, meaning all machines on that subnet).

[Cliff Dungey]

Hi Matt,
I rebooted the server, ensured all laptop clients were set to Local Machine Only and the issue went away.
I have rebooted all laptops over and over and it has not returned...
Strange...


Thanks.
Cliff.

[Cliff Dungey]

Matt,
Can you please check the Mountain server,
When you drill down on the remote network screen, microsoft windows network,@home. the local computer that wingate is installed on and the workgroup name "@home" will not show up on the local Mountain server computer or on any of the remote connections.

I have checked all settings, the connection to the main VPN server is solid now since we replaced the router.

I will send the IPaddress via email.

Thanks.
Cliff.

[MattP]

Hi Cliff,

I logged in and I can see what you're talking about, but I don't think it's a WinGate problem. I opened Windows explorer and tried to browse the network but it said that the network was not accessible, that I didn't have permissions to browse it.

You can try rebooting and see if that fixes anything, if it doesn't see if any of the user permissions have changed.

[Cliff Dungey]

Hi Matt,
I did reboot, checked permissions, I'm sort of lost with this one...
I will check Microsoft and see if there is and answers there.

All other issues seemed to be resolved and running, I will be issuing the licenses next week.

I will let you know what I find.

Thanks.
Cliff.

[Cliff Dungey]

Hi Matt,
This fixed to issue:

You experience the subject difficulty in a peer-to-peer network if you disable NetBIOS over TCP/IP on one or more computers in the workgroup and the Computer Browser service is NOT started on one or more computers in the workgroup.

You may receive the following error when you double-click My Network Places:

<Workgroup Name> is not accessible. You may not have permission to use this network resource.

To resolve the problem, perform the following on every computer in the workgroup:

01. Control Panel / [Network and Internet Connections] / Network Connections.

02. Right-click Local Area Connection and press Properties.

03. Select Internet Protocol (TCP/IP) and press Properties.

04. On the General tab, press Advanced.

05. On the WINS tab, check Enable NetBIOS over TCP/IP and press OK.

06. Press OK and Close.

07. Right-click My Computer and press Manage.

08. Expand Services and Applications.

09. If the Computer Browser service is NOT started, right-click Computer Browser and press Start. Right-click Computer Browser and press Properties. Set Startup type to Automatic and press Apply and OK.

Thanks.
Cliff.

[Cliff Dungey]

F.Y.I

I found this on the Microsoft Support site.
http://support.microsoft.com/kb/889320/EN-US#kb1

Cliff.