Have a windows server 2003 domain controller/file server that I can't seem to access from a VPN. on the affected VPN client (XP Pro w/firewall turned off), I have already manually specified the file server as the DNS server for the VPN connection. I also created host file entries on the client.
When I try to browse the file server using its local host name via windows explorer it just shows a blank page. If I try to add a share name to the path, it gives an error saying the path cannot be found. Same thing happens when doing this via the command line. Mapping drives to shares on the file server gives "the network path was not found". Running the net time command and specifying the file server as the time server gives "the server is not configured for transactions").
If I use the FQDN for any of the above commands and procedures, it behaves correctly.
The really odd thing though is that I can ping the file server using just its host...so why can't I use just its host name to map drives and run the net time command??