VPN - unable to browse network

[rperkins]

Have a Pix w/ VPN concentrator setup on Network.

We can connect to VPN and attach to the Network, but that is where the issue starts.

I can use IP numbers to connect via Radmin or Terminal server and connect to the different servers, but I can't use the server name like I can when connected locally.

When I goto browse the network at home, I can only see my system on the domain with the VPN.

Windows 2000 servers, XP Professional laptop w/ dialup

VPN client on laptop is version 3.6.3a

I am also unable to use my drive mappings or Outlook because it is unable to name resolve.

We do have 2 DC w/ DNS running on the LAN.

Thanks for an information.

 

[brontosaurus]

is your vpn client picking up the correct DNS server IP settings? If so, can you ping those IP's?

 

[rperkins]

I ran a ipconfig/all and it shows the dialup using the Proper DNS server on the LAN

I am able to ping servers and workstations on the dialup.

 

[brontosaurus]

OK. How about opening an NSLOOKUP session and trying to resolve some domain names? Does that work? Are you allowing DNS traffic (port 53 tcp/udp) thru the PIX?

 

[rperkins]

From the LAN connection, this works perfect.

On the VPN connection, it comes back with the right IP numbers, but then has this.

*** DC01.royal.local can't find im01: Non-existent domain


As for the port, I am unsure. I will check on that

 

[brontosaurus]

OK. What do you mean by "it comes back with the right IP numbers"? Do you mean when you start NSLOOKUP, it properly identifies the DNS server and give you a > prompt without any errors?

 

[rperkins]

That is correct.

When I run a ipconfig /all, it will list my network DNS servers with the dialup network adapter.

 

[brontosaurus]

hmm...then you just seem to have a failure locating or retrieving resource records, which definitely explains why you can't map drives or connect outlook. how about setting up logging on the PIX temporarily and sending a couple of queries through? In the meantime, if you're able to ping the relevant IP's, try using the local hosts file until you can figure out what's going on.

 

[rperkins]

FYI... The post 53 UDP/TCP are both open

 

[rperkins]

I have created the HOSTS file and placed in the system

This does work, is this the only solution?

 

[brontosaurus]

well, it shouldn't be. the real solution involves finding out why you can't get name resolution from your DNS server...that's why i suggested the logging, or even packet sniffing, just to see where the failure is.

 

[ianbla]

Have you tried getting the VPN user to run a Sync (Explorer>Tools>Syncronize). Worth a try.