Can't browse Network on VPN - seems to be a rule issue?
- From: "Dave Onex" <dave@xxxxxxxx>
- Date: Thu, 3 May 2007 17:00:34 -0700
Hi;
I'm using ISA 2004 Standard w/SP#3 and a L2TP VPN setup. I can connect no
problem and use RDP to access other machines on the internal network.
The problem seems to be browsing the internal network (using Network
Neighborhood) and connecting to shared resources.
When I browse the only machine that shows up is the VPN client itself and
accessing a network share seems to result in a username & password screen
that I can't seem to get past.
Also, Outlook 2000 can't start up because it can't 'see' the internal
network.
All VPN clients are set to use DHCP (on the ISA server) and DHCP on ISA has
options set for the proper internal DNS servers. I also configured ISA's RAS
connections screen to manually tell it to use internal DNS.
Internal DNS is fine - as long as you are not a VPN user! :-) I went out on
the road to check VPN functionality today and I used the ISA's MMC interface
to monitor the log file when I try to browse the network. I see DENIED for
destination IP's of 239.255.255.255 when trying to browse.
Does anyone know why this is happening or what can cause this?
.
- Follow-Ups:
- Re: Can't browse Network on VPN - seems to be a rule issue?
- From: Phillip Windell
- Re: Can't browse Network on VPN - seems to be a rule issue?
- Prev by Date: Re: site to site connection
- Next by Date: DNS through VPN - I want \\nameofserver instead of \\nameofserver.domain.local
- Previous by thread: Re: site to site connection
- Next by thread: Re: Can't browse Network on VPN - seems to be a rule issue?
- Index(es):
Relevant Pages
|
Loading