VPN - PIX and WinXP

This is Interesting: Free IT Magazines  
Home > Archive > VPN > August 2006 > PIX and WinXP





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author PIX and WinXP
whytwelve13@yahoo.com

2006-08-21, 1:14 am

I have a WinXP machine (192.168.0.20) which is connected to a PIX
firewall (192.168.0.254) on its inside interface (currently eth1). The
default gateway on the machine points to the PIX. When I connect
another machine to eth0 (outside - IP 10.10.10.1) with IP 10.10.10.10
and connect via VPN to the PIX, they can ping themselves (for testing,
I have added two access lists to permit any ip and icmp from any two
machines on any interface) - I can do ping 10.10.10.10 from the
internal machine and get echo-reply from outside and ping 192.168.0.20
from outside and get inside machine. VPN pool is
192.168.1.1-192.168.1.2 with netmask 255.255.255.252. I can access the
Web server on XP machine from the outside machine.

Practically, everything works, except one thing - I cannot browse the
Windows network, e.g. by using Explorer or simply by doing net view
\\computer\share. The latter gives me error 53 - The network path was
not found. If I try using IP address, i.e. net view
\\192.168.0.20\share, it doesn't work, too.

I did not put WINS because XP is not a server OS, thus this is not
possible. I have read that this is necessary in order to do the network
browsing (since pings work, I presume browsing is the problem). I tried
modifying lmhosts and adding the necessary host information to it,
without luck. Can this be solved without using WINS/DNS (if these have
anything to do with the problem, anyway)? I presume broadcast is
limited in VPN connections, so this could also be the problem.

Help is appreciated, thank you!

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com