Prev: install service pack to windows server 2003
Next: non-domain PC on the network
From: jaajog on 12 Jun 2010 05:43
It is probably a routing issue, check the output of 'route print'.
If there is no route for the whole 192.168.1.0 network, only for the server
that is 192.168.1.200, you can try to add route manually to see if that
helps: 'route add 192.168.1.0 mask 255.255.255.0 192.168.1.200'
Change the mask if needed of course.

"john" wrote:

> On Jun 10, 8:49 am, "JohnB" <jbri...(a)yahoo.com> wrote:
> > can you ping 192.168.1.101
> >
> > If so, can you see it's hidden adminstrative share by using
> > \\192.168.1.101\c$
> >
> > If the answer to both is yes, check the share permissions on the folder(s)
> > you're sharing out.
> >
> > "john" <johnbah...(a)hotmail.com> wrote in message
> >
> > news:470464be-0cb9-4ec5-a822-d9cefe2ad47a(a)z8g2000yqz.googlegroups.com...
> >
> > >I have a successful VPN connection to my Sever2k3. The client is XP2.
> > > I can access all the resources on the server with no problem. My
> > > problem is that I cannot access the shared folders on the clients of
> > > the network. I am accessing the sever with
> >
> > > \\192.168.1.200\ which is the address of the server. then when I try
> > > to do the same with the client which is \\192.168.1.101, it does not
> > > connect.
> >
> > > Any ideas?
>
> I could not ping. It gave "request timed out message".
> .
>
From: JohnB on 14 Jun 2010 08:13
Is this server you're trying to reach the shares on, also the VPN server?
Can you ping by IP, any of the other computers on the network that that VPN
server is on?
That's the issue; is your VPN setup working correctly?

Most of the time, VPN clients have to be on a differenet subnet than the
host network.


"john" <johnbahran(a)hotmail.com> wrote in message
news:4bd8ef94-8849-472c-b586-5b7e78d7596c(a)z8g2000yqz.googlegroups.com...
On Jun 10, 3:00 pm, "JohnB" <jbri...(a)yahoo.com> wrote:
> You'll need to describe your network topology better.
> Is this a new VPN setup?
>
> Are you talking about a site-to-site connnection or a client to a site? Is
> the VPN connection working at all?
>
> "john" <johnbah...(a)hotmail.com> wrote in message
>
> news:5cadb18c-505a-492d-b79a-2d3e53517573(a)t10g2000yqg.googlegroups.com...
> On Jun 10, 8:49 am, "JohnB" <jbri...(a)yahoo.com> wrote:
>
>
>
> > can you ping 192.168.1.101
>
> > If so, can you see it's hidden adminstrative share by using
> > \\192.168.1.101\c$
>
> > If the answer to both is yes, check the share permissions on the
> > folder(s)
> > you're sharing out.
>
> > "john" <johnbah...(a)hotmail.com> wrote in message
>
> >news:470464be-0cb9-4ec5-a822-d9cefe2ad47a(a)z8g2000yqz.googlegroups.com...
>
> > >I have a successful VPN connection to my Sever2k3. The client is XP2.
> > > I can access all the resources on the server with no problem. My
> > > problem is that I cannot access the shared folders on the clients of
> > > the network. I am accessing the sever with
>
> > > \\192.168.1.200\ which is the address of the server. then when I try
> > > to do the same with the client which is \\192.168.1.101, it does not
> > > connect.
>
> > > Any ideas?
>
> I could not ping. It gave "request timed out message".

Being VPN it is definitely a client-to-site, however it connects only
to the server as I can only use shares from the server. I cannot get
the shares from any other computers on the network.


From: Grant Taylor on 14 Jun 2010 16:50
On 06/12/10 04:43, jaajog wrote:
> It is probably a routing issue, check the output of 'route print'.
> If there is no route for the whole 192.168.1.0 network, only for the server
> that is 192.168.1.200, you can try to add route manually to see if that
> helps: 'route add 192.168.1.0 mask 255.255.255.0 192.168.1.200'
> Change the mask if needed of course.

Agreed.

Though I think the client is going to have a route through the VPN to
the other systems on the LAN. I think the problem is going to be that
the other systems on the LAN will not have a route back to the VPN client.

I.e. if the LAN server and workstations are using a SOHO (NATing) router
(configured to forward VPN traffic to the server) as their default
gateway to access the internet it is very unlikely that the workstations
will have a route back to the VPN client.

What is most likely happening is that the VPN client has established a
VPN to the server and thus has a route to the server and to the LAN
subnet. However the other workstations on the LAN only have a default
route via the router. So the workstations don't know to send the
traffic back to the server to get back to the VPN client.

Try establishing a route to the VPN client on one of the workstations
via the server.

This is all of course assuming that your VPN is routing and not bridging
in to the office LAN / subnet.

What is an example IP of a workstation on the network?

What is an example IP that the VPN client gets when the VPN is established?



Grant. . . .


P.S. Sorry for the delay. For some reason, my post(s) did not get
propagated between news servers. So I'm re-posting this to a different
server.
First  |  Prev  | 
Pages: 1 2
Prev: install service pack to windows server 2003
Next: non-domain PC on the network