Computer not accessible

Forum for all technical support and trouble shooting of the WinGate VPN.

Moderator: Qbik Staff

Computer not accessible

Postby Refuge » Nov 02 05 5:14 am

Hi,

We have a one user licence at both ends of our setup. Have configured the networks on different subnets. Both ends have a network, but only one computer at each end needs to take part.

IP Addresses on host = 192.168.0.x
IP Addresses on remote = 192.168.1.x

I an negotiate an SSL channel easily and can see the machine, but when I want to use any of the shares on it, I can't. It comes back with not accessible.

The machine I am connecting to with the Wingate on is the machine I want to access the shares on.

Any ideas?
Refuge
 
Posts: 4
Joined: Oct 28 05 2:24 am

Postby MattP » Nov 02 05 9:33 am

Can you ping the remote machine by name? If not, can you ping by IP address?

Is port 809 UDP mapped through to the host machine?

Can you make sure that file and print sharing and NetBIOS over TCP/IP enabled for the external adapter on the host machine?

Are you able to browse the shares on the remote machine from the host machine?

Are you running any firewalls (including the XP SP2 firewall) on either of the machines? If so, try stopping them and see if that helps?
MattP
Qbik Staff
 
Posts: 991
Joined: Sep 08 03 4:30 pm

Not Aceessible

Postby Refuge » Nov 03 05 10:25 pm

I can ping by ip address but not by name.

No firewalls are stopiing traffic

It is definately ported through on port 809.

It is NT4 server so no XP SP2 issues.

The netbios over tcpip is enabled

It was working fine when i set it up and now it just won't connect.
Refuge
 
Posts: 4
Joined: Oct 28 05 2:24 am

Postby adrien » Nov 03 05 10:41 pm

Hi

With single user licenses, you can't publish network routes, so the only machine that can participate in the VPN at each end in your scenario is the machine with the VPN software installed on it.

So there should be no routing issues, or broadcast issues. since you can ping this machine by IP, it indicates that the IP tunnelling is working, if you can't by name, then have you checked that UDP broadcast relaying is turned on on each end?

Also, Wingate VPN 2.1.0 is a recommended update. We solved several VPN problems.

Adrien
adrien
Qbik Staff
 
Posts: 5441
Joined: Sep 03 03 2:54 pm
Location: Auckland


Return to WinGate VPN

Who is online

Users browsing this forum: No registered users and 43 guests

cron