VPN....NW

Hello,

We have a simple vpn solution...A Linksys router on the
Corp. side and a vpn connection on all client/home
machines with a mapped drive to the Corp. Server. It has
worked fine for several months until now. We can still
establish a vpn connection but can no longer browse
resources on the server through explorer.I have tried
remapping the drive and also tried typing the server name
or ip address in the run command window to no avail.All
client computer names are in ad and the Gateway box under
tcpip properties checked. I can establish a Remote
Desktop Connection to the server. However, for obvious
reasons we do not want clients having access to the
server desktop. We have made no major changes to the NW
or the Servers other than adding SP1 to our exchange
server recently. We are running Windows 2003 std server.
All clients run XP professional with SP1.

Would appreciate any feedback.

JimB:

Did you change anything in the WINS tab of the TCP/IP properties of the
server or clients? Browsing problems are usually NetBIOS or WINS problems.
From what I've gathered from previous postings, network browsing is not
reliable without WINS - even if you have all XP clients and 2003 servers.
Try playing around with the LMHOSTS file on the clients and see if that gets
you anywhere. If that works and you only have a handful of VPN clients, then
manually maintaining the lmhosts files wouldn't be that bad. If you have
many VPN clients, then you'll need to set up a WINS server, which is pretty
straightforward to do.

Regards,
Martin

"JimB" <(E-Mail Removed)> wrote in message
news:2c98401c46995$c2c1f070$(E-Mail Removed)...
> Hello,
>
> We have a simple vpn solution...A Linksys router on the
> Corp. side and a vpn connection on all client/home
> machines with a mapped drive to the Corp. Server. It has
> worked fine for several months until now. We can still
> establish a vpn connection but can no longer browse
> resources on the server through explorer.I have tried
> remapping the drive and also tried typing the server name
> or ip address in the run command window to no avail.All
> client computer names are in ad and the Gateway box under
> tcpip properties checked. I can establish a Remote
> Desktop Connection to the server. However, for obvious
> reasons we do not want clients having access to the
> server desktop. We have made no major changes to the NW
> or the Servers other than adding SP1 to our exchange
> server recently. We are running Windows 2003 std server.
> All clients run XP professional with SP1.
>
> Would appreciate any feedback.

Martin,
Haven't made any changes to Wins.....I don't have any
lmhost files configured and we are not using Wins at the
moment. I will try configuring a host file.....just a bit
perplexed on why it has been working just fine up until
now.

Thanks Martin.

>-----Original Message-----
>JimB:
>
>Did you change anything in the WINS tab of the TCP/IP
properties of the
>server or clients? Browsing problems are usually NetBIOS
or WINS problems.
>From what I've gathered from previous postings, network
browsing is not
>reliable without WINS - even if you have all XP clients
and 2003 servers.
>Try playing around with the LMHOSTS file on the clients
and see if that gets
>you anywhere. If that works and you only have a handful
of VPN clients, then
>manually maintaining the lmhosts files wouldn't be that
bad. If you have
>many VPN clients, then you'll need to set up a WINS
server, which is pretty
>straightforward to do.
>
>Regards,
>Martin
>
>"JimB" <(E-Mail Removed)> wrote in
message
>news:2c98401c46995$c2c1f070$(E-Mail Removed)...
>> Hello,
>>
>> We have a simple vpn solution...A Linksys router on the
>> Corp. side and a vpn connection on all client/home
>> machines with a mapped drive to the Corp. Server. It
has
>> worked fine for several months until now. We can still
>> establish a vpn connection but can no longer browse
>> resources on the server through explorer.I have tried
>> remapping the drive and also tried typing the server
name
>> or ip address in the run command window to no avail.All
>> client computer names are in ad and the Gateway box
under
>> tcpip properties checked. I can establish a Remote
>> Desktop Connection to the server. However, for obvious
>> reasons we do not want clients having access to the
>> server desktop. We have made no major changes to the NW
>> or the Servers other than adding SP1 to our exchange
>> server recently. We are running Windows 2003 std
server.
>> All clients run XP professional with SP1.
>>
>> Would appreciate any feedback.
>
>
>.
>

You might want to check DNS as well. If your running DHCP
but your clients are static you might want to tuen off
DHCP. Also in regards to LMHOST. That is an excelent way
to have a server recognise a client(s). I use that for a
connection to another contry that is very very slow. And
VPN is impossible wtihout it.

Tom
>-----Original Message-----
>Martin,
>Haven't made any changes to Wins.....I don't have any
>lmhost files configured and we are not using Wins at the
>moment. I will try configuring a host file.....just a
bit
>perplexed on why it has been working just fine up until
>now.
>
>Thanks Martin.
>
>>-----Original Message-----
>>JimB:
>>
>>Did you change anything in the WINS tab of the TCP/IP
>properties of the
>>server or clients? Browsing problems are usually
NetBIOS
>or WINS problems.
>>From what I've gathered from previous postings, network
>browsing is not
>>reliable without WINS - even if you have all XP clients
>and 2003 servers.
>>Try playing around with the LMHOSTS file on the clients
>and see if that gets
>>you anywhere. If that works and you only have a handful
>of VPN clients, then
>>manually maintaining the lmhosts files wouldn't be that
>bad. If you have
>>many VPN clients, then you'll need to set up a WINS
>server, which is pretty
>>straightforward to do.
>>
>>Regards,
>>Martin
>>
>>"JimB" <(E-Mail Removed)> wrote in
>message
>>news:2c98401c46995$c2c1f070$(E-Mail Removed).. .
>>> Hello,
>>>
>>> We have a simple vpn solution...A Linksys router on
the
>>> Corp. side and a vpn connection on all client/home
>>> machines with a mapped drive to the Corp. Server. It
>has
>>> worked fine for several months until now. We can still
>>> establish a vpn connection but can no longer browse
>>> resources on the server through explorer.I have tried
>>> remapping the drive and also tried typing the server
>name
>>> or ip address in the run command window to no
avail.All
>>> client computer names are in ad and the Gateway box
>under
>>> tcpip properties checked. I can establish a Remote
>>> Desktop Connection to the server. However, for obvious
>>> reasons we do not want clients having access to the
>>> server desktop. We have made no major changes to the
NW
>>> or the Servers other than adding SP1 to our exchange
>>> server recently. We are running Windows 2003 std
>server.
>>> All clients run XP professional with SP1.
>>>
>>> Would appreciate any feedback.
>>
>>
>>.
>>
>.
>

I have been using my SonicWall VPN client for more that a year with
Win XP Pro. Approx 2 months ago I noticed that my VPN connection was
established however no data transfer could occur. I have tried
entering a diff. Pre-Shared secret (key) and notice that the VPN
connectivity is lost, so I know that my key is good. I wonder if an
XP update has done something to the state of my VPN connection? My
internet service works fine.

Any ideas???

Samuel


"Tom" <(E-Mail Removed)> wrote in message news:<2c2bb01c469bf$25b22b40$(E-Mail Removed)>...
> You might want to check DNS as well. If your running DHCP
> but your clients are static you might want to tuen off
> DHCP. Also in regards to LMHOST. That is an excelent way
> to have a server recognise a client(s). I use that for a
> connection to another contry that is very very slow. And
> VPN is impossible wtihout it.
>
> Tom
> >-----Original Message-----
> >Martin,
> >Haven't made any changes to Wins.....I don't have any
> >lmhost files configured and we are not using Wins at the
> >moment. I will try configuring a host file.....just a
> bit
> >perplexed on why it has been working just fine up until
> >now.
> >
> >Thanks Martin.
> >
> >>-----Original Message-----
> >>JimB:
> >>
> >>Did you change anything in the WINS tab of the TCP/IP
> properties of the
> >>server or clients? Browsing problems are usually
> NetBIOS
> or WINS problems.
> >>From what I've gathered from previous postings, network
> browsing is not
> >>reliable without WINS - even if you have all XP clients
> and 2003 servers.
> >>Try playing around with the LMHOSTS file on the clients
> and see if that gets
> >>you anywhere. If that works and you only have a handful
> of VPN clients, then
> >>manually maintaining the lmhosts files wouldn't be that
> bad. If you have
> >>many VPN clients, then you'll need to set up a WINS
> server, which is pretty
> >>straightforward to do.
> >>
> >>Regards,
> >>Martin
> >>
> >>"JimB" <(E-Mail Removed)> wrote in
> message
> >>news:2c98401c46995$c2c1f070$(E-Mail Removed).. .
> >>> Hello,
> >>>
> >>> We have a simple vpn solution...A Linksys router on
> the
> >>> Corp. side and a vpn connection on all client/home
> >>> machines with a mapped drive to the Corp. Server. It
> has
> >>> worked fine for several months until now. We can still
> >>> establish a vpn connection but can no longer browse
> >>> resources on the server through explorer.I have tried
> >>> remapping the drive and also tried typing the server
> name
> >>> or ip address in the run command window to no
> avail.All
> >>> client computer names are in ad and the Gateway box
> under
> >>> tcpip properties checked. I can establish a Remote
> >>> Desktop Connection to the server. However, for obvious
> >>> reasons we do not want clients having access to the
> >>> server desktop. We have made no major changes to the
> NW
> >>> or the Servers other than adding SP1 to our exchange
> >>> server recently. We are running Windows 2003 std
> server.
> >>> All clients run XP professional with SP1.
> >>>
> >>> Would appreciate any feedback.
> >>
> >>
> >>.
> >>
> >.
> >

Hi Samuel:

WinXP has a built-in firewall, and some service pack updates could
turn it on, so check it inside the the Advanced tab of your LAN TCP/IP
properties.

Also, make sure you test your VPN by pinging the inside IP of the VPN
firewall you are connecting to.


(E-Mail Removed) (Samuel Montana) wrote in message news:<(E-Mail Removed). com>...
> I have been using my SonicWall VPN client for more that a year with
> Win XP Pro. Approx 2 months ago I noticed that my VPN connection was
> established however no data transfer could occur. I have tried
> entering a diff. Pre-Shared secret (key) and notice that the VPN
> connectivity is lost, so I know that my key is good. I wonder if an
> XP update has done something to the state of my VPN connection? My
> internet service works fine.
>
> Any ideas???
>
> Samuel
>
>
> "Tom" <(E-Mail Removed)> wrote in message news:<2c2bb01c469bf$25b22b40$(E-Mail Removed)>...
> > You might want to check DNS as well. If your running DHCP
> > but your clients are static you might want to tuen off
> > DHCP. Also in regards to LMHOST. That is an excelent way
> > to have a server recognise a client(s). I use that for a
> > connection to another contry that is very very slow. And
> > VPN is impossible wtihout it.
> >
> > Tom
> > >-----Original Message-----
> > >Martin,
> > >Haven't made any changes to Wins.....I don't have any
> > >lmhost files configured and we are not using Wins at the
> > >moment. I will try configuring a host file.....just a
> bit
> > >perplexed on why it has been working just fine up until
> > >now.
> > >
> > >Thanks Martin.
> > >
> > >>-----Original Message-----
> > >>JimB:
> > >>
> > >>Did you change anything in the WINS tab of the TCP/IP
> properties of the
> > >>server or clients? Browsing problems are usually
> > NetBIOS
> > or WINS problems.
> > >>From what I've gathered from previous postings, network
> browsing is not
> > >>reliable without WINS - even if you have all XP clients
> and 2003 servers.
> > >>Try playing around with the LMHOSTS file on the clients
> and see if that gets
> > >>you anywhere. If that works and you only have a handful
> of VPN clients, then
> > >>manually maintaining the lmhosts files wouldn't be that
> bad. If you have
> > >>many VPN clients, then you'll need to set up a WINS
> server, which is pretty
> > >>straightforward to do.
> > >>
> > >>Regards,
> > >>Martin
> > >>
> > >>"JimB" <(E-Mail Removed)> wrote in
> message
> > >>news:2c98401c46995$c2c1f070$(E-Mail Removed).. .
> > >>> Hello,
> > >>>
> > >>> We have a simple vpn solution...A Linksys router on
> the
> > >>> Corp. side and a vpn connection on all client/home
> > >>> machines with a mapped drive to the Corp. Server. It
> has
> > >>> worked fine for several months until now. We can still
> > >>> establish a vpn connection but can no longer browse
> > >>> resources on the server through explorer.I have tried
> > >>> remapping the drive and also tried typing the server
> name
> > >>> or ip address in the run command window to no
> avail.All
> > >>> client computer names are in ad and the Gateway box
> under
> > >>> tcpip properties checked. I can establish a Remote
> > >>> Desktop Connection to the server. However, for obvious
> > >>> reasons we do not want clients having access to the
> > >>> server desktop. We have made no major changes to the
> NW
> > >>> or the Servers other than adding SP1 to our exchange
> > >>> server recently. We are running Windows 2003 std
> server.
> > >>> All clients run XP professional with SP1.
> > >>>
> > >>> Would appreciate any feedback.
> > >>
> > >>
> > >>.
> > >>
> > >.
> > >

My laptop roams with me between my client site, which has an unsecured
wireless Internet connection, and home which is behind a Linksys
Wireless router.

I can VPN into the PIX at the office from home and the client site,
but cannot access Windows network shares or Exchange.

After sorting out IP addressing problems (192.168.1.x was being used
locally at home as well as behind the PIX at work) my VPN sets up fine
using the Cisco ver 3.xxx client from home and I can ping my exhange
server through the VPN tunnel - even telnet to port 25 on the exchange
server.

What I cannot do from home (behind the Linksys) is connect to the
Exchange server using Outlook, or browse network shares.

Any ideas??

(E-Mail Removed) (wailakig) wrote in message news:<(E-Mail Removed). com>...
> Hi Samuel:
>
> WinXP has a built-in firewall, and some service pack updates could
> turn it on, so check it inside the the Advanced tab of your LAN TCP/IP
> properties.
>
> Also, make sure you test your VPN by pinging the inside IP of the VPN
> firewall you are connecting to.
>
>
> (E-Mail Removed) (Samuel Montana) wrote in message news:<(E-Mail Removed). com>...
> > I have been using my SonicWall VPN client for more that a year with
> > Win XP Pro. Approx 2 months ago I noticed that my VPN connection was
> > established however no data transfer could occur. I have tried
> > entering a diff. Pre-Shared secret (key) and notice that the VPN
> > connectivity is lost, so I know that my key is good. I wonder if an
> > XP update has done something to the state of my VPN connection? My
> > internet service works fine.
> >
> > Any ideas???
> >
> > Samuel
> >
> >
> > "Tom" <(E-Mail Removed)> wrote in message news:<2c2bb01c469bf$25b22b40$(E-Mail Removed)>...
> > > You might want to check DNS as well. If your running DHCP
> > > but your clients are static you might want to tuen off
> > > DHCP. Also in regards to LMHOST. That is an excelent way
> > > to have a server recognise a client(s). I use that for a
> > > connection to another contry that is very very slow. And
> > > VPN is impossible wtihout it.
> > >
> > > Tom
> > > >-----Original Message-----
> > > >Martin,
> > > >Haven't made any changes to Wins.....I don't have any
> > > >lmhost files configured and we are not using Wins at the
> > > >moment. I will try configuring a host file.....just a
> bit
> > > >perplexed on why it has been working just fine up until
> > > >now.
> > > >
> > > >Thanks Martin.
> > > >
> > > >>-----Original Message-----
> > > >>JimB:
> > > >>
> > > >>Did you change anything in the WINS tab of the TCP/IP
> properties of the
> > > >>server or clients? Browsing problems are usually
> > > NetBIOS
> > > or WINS problems.
> > > >>From what I've gathered from previous postings, network
> browsing is not
> > > >>reliable without WINS - even if you have all XP clients
> and 2003 servers.
> > > >>Try playing around with the LMHOSTS file on the clients
> and see if that gets
> > > >>you anywhere. If that works and you only have a handful
> of VPN clients, then
> > > >>manually maintaining the lmhosts files wouldn't be that
> bad. If you have
> > > >>many VPN clients, then you'll need to set up a WINS
> server, which is pretty
> > > >>straightforward to do.
> > > >>
> > > >>Regards,
> > > >>Martin
> > > >>
> > > >>"JimB" <(E-Mail Removed)> wrote in
> message
> > > >>news:2c98401c46995$c2c1f070$(E-Mail Removed).. .
> > > >>> Hello,
> > > >>>
> > > >>> We have a simple vpn solution...A Linksys router on
> the
> > > >>> Corp. side and a vpn connection on all client/home
> > > >>> machines with a mapped drive to the Corp. Server. It
> has
> > > >>> worked fine for several months until now. We can still
> > > >>> establish a vpn connection but can no longer browse
> > > >>> resources on the server through explorer.I have tried
> > > >>> remapping the drive and also tried typing the server
> name
> > > >>> or ip address in the run command window to no
> avail.All
> > > >>> client computer names are in ad and the Gateway box
> under
> > > >>> tcpip properties checked. I can establish a Remote
> > > >>> Desktop Connection to the server. However, for obvious
> > > >>> reasons we do not want clients having access to the
> > > >>> server desktop. We have made no major changes to the
> NW
> > > >>> or the Servers other than adding SP1 to our exchange
> > > >>> server recently. We are running Windows 2003 std
> server.
> > > >>> All clients run XP professional with SP1.
> > > >>>
> > > >>> Would appreciate any feedback.
> > > >>
> > > >>
> > > >>.
> > > >>
> > > >.
> > > >