Can't see shared via VPN on "some" clients

Hi Folks,
I'm stumped .... I've been trying to figure out why .... when I take a new
box, XP Pro and create the VPN connection and connect just dandy, these new
systems can't see the network shares. All of my old connections could and
still can from other systems.

I'm stumped, if I add the PC to the domain, its a happy camper but on a
diff. subnet it runs fine and the connection comes right up but again they
can't see the shares .... its prob. something really obvious but I've been at
it for a while and I am at a loss .... (grin)

Cheers'
Dave Cason

It is probably a name resolution problem. VPN clients can't use
broadcasts for this, so they need to be able to use either DNS or WINS.

If they get the correct DNS server address when they connect they should
be able to resolve names on the LAN using DNS. Note that they will need to
have the correct DNS suffix in the connection properties to be able to see
machines using just the machine name.


"Dave Cason" <Dave (E-Mail Removed)> wrote in message
news:F1A9D9F2-1CA1-48D5-828F-(E-Mail Removed)...
> Hi Folks,
> I'm stumped .... I've been trying to figure out why .... when I take a
> new
> box, XP Pro and create the VPN connection and connect just dandy, these
> new
> systems can't see the network shares. All of my old connections could and
> still can from other systems.
>
> I'm stumped, if I add the PC to the domain, its a happy camper but on a
> diff. subnet it runs fine and the connection comes right up but again they
> can't see the shares .... its prob. something really obvious but I've been
> at
> it for a while and I am at a loss .... (grin)
>
> Cheers'
> Dave Cason

Hi Bill.

Well I don't "think" its DNS but maybe .... it's odd, I have my old
conneciton on my PC at home to the office .... fire it up and connect to the
VPN at work and browse away ...no problem ....

Create a new connection on another XP box .... pretty much same kinda stuff
and can't get anyplace .... It starts and connects but I can't browse any
shares ....

And I'm still stumped .... (grin) Anything specific I should look for?

Cheers'
Dave


"Bill Grant" wrote:

> It is probably a name resolution problem. VPN clients can't use
> broadcasts for this, so they need to be able to use either DNS or WINS.
>
> If they get the correct DNS server address when they connect they should
> be able to resolve names on the LAN using DNS. Note that they will need to
> have the correct DNS suffix in the connection properties to be able to see
> machines using just the machine name.
>
>
> "Dave Cason" <Dave (E-Mail Removed)> wrote in message
> news:F1A9D9F2-1CA1-48D5-828F-(E-Mail Removed)...
> > Hi Folks,
> > I'm stumped .... I've been trying to figure out why .... when I take a
> > new
> > box, XP Pro and create the VPN connection and connect just dandy, these
> > new
> > systems can't see the network shares. All of my old connections could and
> > still can from other systems.
> >
> > I'm stumped, if I add the PC to the domain, its a happy camper but on a
> > diff. subnet it runs fine and the connection comes right up but again they
> > can't see the shares .... its prob. something really obvious but I've been
> > at
> > it for a while and I am at a loss .... (grin)
> >
> > Cheers'
> > Dave Cason
>
>

Hi Again Bill ....

I just connected both and here's the settigns I got via both VPN's

My working system .... PPP adapter vauntcom:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.104
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.10
Primary WINS Server . . . . . . . : 192.168.1.10


The box that's not working ......PPP adapter Virtual Private Network
Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 192.168.1.101
DNS Servers . . . . . . . . . . . : 192.168.1.10
Primary WINS Server . . . . . . . : 192.168.1.10


I see that the one has a gateway and one doesen't .... any idea ?

Cheers'
Dave



"Bill Grant" wrote:

> It is probably a name resolution problem. VPN clients can't use
> broadcasts for this, so they need to be able to use either DNS or WINS.
>
> If they get the correct DNS server address when they connect they should
> be able to resolve names on the LAN using DNS. Note that they will need to
> have the correct DNS suffix in the connection properties to be able to see
> machines using just the machine name.
>
>
> "Dave Cason" <Dave (E-Mail Removed)> wrote in message
> news:F1A9D9F2-1CA1-48D5-828F-(E-Mail Removed)...
> > Hi Folks,
> > I'm stumped .... I've been trying to figure out why .... when I take a
> > new
> > box, XP Pro and create the VPN connection and connect just dandy, these
> > new
> > systems can't see the network shares. All of my old connections could and
> > still can from other systems.
> >
> > I'm stumped, if I add the PC to the domain, its a happy camper but on a
> > diff. subnet it runs fine and the connection comes right up but again they
> > can't see the shares .... its prob. something really obvious but I've been
> > at
> > it for a while and I am at a loss .... (grin)
> >
> > Cheers'
> > Dave Cason
>
>

Well the one with the default gateway set is correct for a Microsoft VPN
connection. The default gateway should be the "received" IP address of the
PPP connection. That simply means that the default gateway is the PPP
connection (which is what it should be) and that all non-local traffic will
go over the VPN connection. I have no idea how the connection without a
default gateway would work.

"Dave Cason" <Dave (E-Mail Removed)> wrote in message
news:4B6A1A61-3264-409C-BB23-(E-Mail Removed)...
>
> Hi Again Bill ....
>
> I just connected both and here's the settigns I got via both VPN's
>
> My working system .... PPP adapter vauntcom:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.104
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
> DNS Servers . . . . . . . . . . . : 192.168.1.10
> Primary WINS Server . . . . . . . : 192.168.1.10
>
>
> The box that's not working ......PPP adapter Virtual Private Network
> Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> Dhcp Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.101
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . : 192.168.1.101
> DNS Servers . . . . . . . . . . . : 192.168.1.10
> Primary WINS Server . . . . . . . : 192.168.1.10
>
>
> I see that the one has a gateway and one doesen't .... any idea ?
>
> Cheers'
> Dave
>
>
>
> "Bill Grant" wrote:
>
>> It is probably a name resolution problem. VPN clients can't use
>> broadcasts for this, so they need to be able to use either DNS or WINS.
>>
>> If they get the correct DNS server address when they connect they
>> should
>> be able to resolve names on the LAN using DNS. Note that they will need
>> to
>> have the correct DNS suffix in the connection properties to be able to
>> see
>> machines using just the machine name.
>>
>>
>> "Dave Cason" <Dave (E-Mail Removed)> wrote in message
>> news:F1A9D9F2-1CA1-48D5-828F-(E-Mail Removed)...
>> > Hi Folks,
>> > I'm stumped .... I've been trying to figure out why .... when I take a
>> > new
>> > box, XP Pro and create the VPN connection and connect just dandy, these
>> > new
>> > systems can't see the network shares. All of my old connections could
>> > and
>> > still can from other systems.
>> >
>> > I'm stumped, if I add the PC to the domain, its a happy camper but on a
>> > diff. subnet it runs fine and the connection comes right up but again
>> > they
>> > can't see the shares .... its prob. something really obvious but I've
>> > been
>> > at
>> > it for a while and I am at a loss .... (grin)
>> >
>> > Cheers'
>> > Dave Cason
>>
>>