VPN Windows Browsing Issues?

  • Thread starter Thread starter Ashley Heaton
  • Start date Start date
A

Ashley Heaton

We have got a windows 2003 server setup on it's own
domain that is running RAS for VPN only.

We have it trusted with our main domain and that appears
to be working and tests fine.

We can log into the VPN using accounts from either domain
and we can access everything on both sides via
\\ipaddress.

We cannot however use the FQDN of a host to connect to
it's shares on the main domain side. So if I put in
\\machinename.domainname.com when connected to the VPN it
takes around 20 seconds and then it brings up a blank
explorer window with the machine name as the path and 0
items displayed. If I change to using the IP address
however it comes up in about 5 seconds and displays all
the shares.

The servers we are trying to access are a mix of windows
2000 and 2003 servers. The Primary DNS servers on both
sides of the trust are windows 2003 and have the
conditional forwarding setup to point to each other for
each domain respectivly

Please let me know what I'm missing or what I can check
to find out what might be happening here. I can ping the
FQDN of the servers in question.

Thanks in advance.
 
Can you ping the machine with the "machine name"?
If no, there is some name resolution problem with the DNS/DHCP.

Send us info on the output of ping with "machine name" and ipaddress.

And also the route print to the ipaddress you want to access.
 
I CAN ping the FQDN of the servers I'm trying to access.
It resolves correctly every time.

I'm not familiar with the route print command.

Is the syntax c:\route print ipaddress?

Thanks,

Ashley Heaton
 
Back
Top