Koozali.org: home of the SME Server

Remote Windows File Sharing

Offline Graham

  • ****
  • 105
  • +0/-0
Re: Remote Windows File Sharing
« Reply #15 on: September 26, 2007, 01:32:27 PM »
I'm entering the LAN IP 10.0.1.1, the IP the VPN gets given is 10.0.1.246.

The Client PC isn’t’ running any protection at the moment not even windows firewall

« Last Edit: September 26, 2007, 01:51:45 PM by sprattgraham »

Offline Graham

  • ****
  • 105
  • +0/-0
Re: Remote Windows File Sharing
« Reply #16 on: September 26, 2007, 01:42:45 PM »
I also can't ping the VPN client from the Local Network, or from the SME Server

Pinging 10.0.1.246 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.0.1.246: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Offline chris burnat

  • *****
  • 1,135
  • +2/-0
    • http://www.burnat.com
Re: Remote Windows File Sharing
« Reply #17 on: September 26, 2007, 02:17:02 PM »
I'm entering the LAN IP 10.0.1.1, the IP the VPN gets given is 10.0.1.246.
The Client PC isn’t’ running any protection at the moment not even windows firewall


You could have hit a Bug.  Please go to the Bugtracker and fill a report there, providing a summary of what you are experiencing, In particular the fact that you can lconnect OK with VPN, but cannot ping the SME server from the VPN client.  Also provide version number of your server, and history if you can.
Thanks
chris
- chris
If it does not work out of the box, please fill in a Bug Report @ Bugzilla (http://bugs.contribs.org)  - check: http://wiki.contribs.org/Bugzilla_Help .  Thanks.

Offline Graham

  • ****
  • 105
  • +0/-0
Re: Remote Windows File Sharing
« Reply #18 on: September 26, 2007, 02:32:15 PM »

Offline maykelsoft

  • *
  • 57
  • +0/-0
    • http://www.esi.com.ph
Re: Remote Windows File Sharing
« Reply #19 on: September 26, 2007, 02:57:04 PM »
Hi,

I am using PPTP VPN with no problem at all. I can access our LAN shares via remote. Please give the following info:
1. On your remote machine try ipconfig /all -- post what you got
2. Are you able to browse internet while connected to your SME VPN Server?
3. You said that there's no firewall enable on your machine, as I read the threads it looks that only firewall can block that services... or your remote machine is not connected at all... strange!
4. Is there any unusual on your /var/logs/messages?

I know that this issue is already reported on bug tracker... just want to help quick.

Regards,
Mike

Offline Graham

  • ****
  • 105
  • +0/-0
Re: Remote Windows File Sharing
« Reply #20 on: September 26, 2007, 03:09:03 PM »
Thats correct the client has no Firewall, and I can still access the Internet fine on the VPN Client

PPP adapter Spratt-Family:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
   Physical Address. . . . . . . . . : 00-53-45-00-00-00
   DHCP Enabled. . . . . . . . . . . : No
   IP Address. . . . . . . . . . . . : 10.0.1.246
   Subnet Mask . . . . . . . . . . . : 255.255.255.255
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 10.0.1.1
                                       10.0.1.1
   Primary WINS Server . . . . . . . : 10.0.1.1
   Secondary WINS Server . . . . . . : 10.0.1.1
« Last Edit: September 26, 2007, 03:14:50 PM by sprattgraham »

Offline maykelsoft

  • *
  • 57
  • +0/-0
    • http://www.esi.com.ph
Re: Remote Windows File Sharing
« Reply #21 on: September 26, 2007, 03:15:23 PM »
Hmm looks the same as mine... are you using M$ Vista on your remote machine?

I believe this is a firewall issue on your remote machine if you are using M$ Vista.

Offline Graham

  • ****
  • 105
  • +0/-0
Re: Remote Windows File Sharing
« Reply #22 on: September 26, 2007, 03:19:29 PM »
Hmm looks the same as mine... are you using M$ Vista on your remote machine?

I believe this is a firewall issue on your remote machine if you are using M$ Vista.


No Windows 2003 Server, Windows Firewall is Disabled and RRAR is as Disabled

Offline maykelsoft

  • *
  • 57
  • +0/-0
    • http://www.esi.com.ph
Re: Remote Windows File Sharing
« Reply #23 on: September 26, 2007, 03:25:28 PM »
What are the other services running on your windows 2003 server? AD? DHCP? WINS? DNS?

Try this command on windows 2003 server command prompt:
net dom query fsmo



« Last Edit: September 26, 2007, 03:27:00 PM by maykelsoft »

Offline Graham

  • ****
  • 105
  • +0/-0
Re: Remote Windows File Sharing
« Reply #24 on: September 26, 2007, 03:31:13 PM »
This doesn't seem to work, "net dom query fsmo"

I've tried from a few different 2003 Servers the latest server I'm using isn't running AD, DHCP, WINS or DNS

Offline maykelsoft

  • *
  • 57
  • +0/-0
    • http://www.esi.com.ph
Re: Remote Windows File Sharing
« Reply #25 on: September 26, 2007, 03:41:56 PM »
Sorry it should be: netdom query fsmo

As you said, there are no other services running on your server.

By the way, you said that you can browse internet while connected to SME VPN. Is there any proxy set to your remote machine browser?

Try the following command from your remote machine:
1. telnet IP_OF_SME_VPN_SERVER 3128
2. tracert www.google.com

I don't believe that you can browse internet on your remote machine using SME VPN server if you can't ping that server itself.

My two cents.

Regards,

mike

Offline Graham

  • ****
  • 105
  • +0/-0
Re: Remote Windows File Sharing
« Reply #26 on: September 26, 2007, 03:51:43 PM »
Sorry it should be: netdom query fsmo

As you said, there are no other services running on your server.

By the way, you said that you can browse internet while connected to SME VPN. Is there any proxy set to your remote machine browser?

Try the following command from your remote machine:
1. telnet IP_OF_SME_VPN_SERVER 3128
2. tracert www.google.com

I don't believe that you can browse internet on your remote machine using SME VPN server if you can't ping that server itself.

My two cents.

Regards,

mike

When browsing the internet on the remote machine it's using it’s gateway not the SME server

This command also doesn’t work “netdom query fsmo”

This command “telnet 10.0.1.1 3128” returns fail to connect

Offline maykelsoft

  • *
  • 57
  • +0/-0
    • http://www.esi.com.ph
Re: Remote Windows File Sharing
« Reply #27 on: September 26, 2007, 04:04:58 PM »
If that's the case. It looks like you are not really connected with SME VPN Server. If your are connected with SME VPN server it automatically set your SME VPN server as your gateway on your remote machine, unless you have changed something in your pptpd.conf.

Try to connect using different machine if possible, just to isolate if this is an issue with your current windows 2003 server or SME VPN server. In case you can connect using different machine, apparently there's a problem with your windows 2003 server.


Offline chris burnat

  • *****
  • 1,135
  • +2/-0
    • http://www.burnat.com
Re: Remote Windows File Sharing
« Reply #28 on: September 27, 2007, 02:39:44 AM »
This issue appears to have been resolved. 
From Bug #3426 at Bugzilla:

Quote
Fixed it, check this URL
http://www.isaserver.org/tutorials/Solving_the_Mystery_of_the_VPNRASWeb_Proxy_Client.html

section "Changing the Gateway Settings"

Edit: added words "appears to have"
« Last Edit: September 27, 2007, 06:11:48 AM by burnat »
- chris
If it does not work out of the box, please fill in a Bug Report @ Bugzilla (http://bugs.contribs.org)  - check: http://wiki.contribs.org/Bugzilla_Help .  Thanks.

Offline judgej

  • *
  • 375
  • +0/-0
Re: Remote Windows File Sharing
« Reply #29 on: September 27, 2007, 07:33:14 PM »
If that's the case. It looks like you are not really connected with SME VPN Server. If your are connected with SME VPN server it automatically set your SME VPN server as your gateway on your remote machine.

I think that depends on the settings on your client machine, rather than the server (or perhaps both). In the VPN connection settings, there is usually a box to tick, to specify whether you want the machine to switch its default gateway to the VPN once it is connected, or to keep the default gateway set to whatever it was before the VPN connected.
-- Jason