A common problem when dealing with Windows networking and a VPN or firewall is that your workstation cannot access the domain controller. Not having all the details, I'll try to address the problem in general.
Windows systems register themselveswith the WINS database when they boot up. The WINS server is usually inside your firewall/VPN. Until you dial-in and start the VPN client, you do not have access to the WINS server. This keeps the workstation from registering with the WINS server. This can cause difficulties.
Once the VPN tunnel is established, as long as your WINS server entry is correct, the workstation should be able to look up a list of domain controllers from the WINS server. At this point, you will be able to logon to the domain.
A workaround for NT is to take the workstation on site and logon to the domain without the VPN. This will cache a copy of your domain credentials on the local workstation. In the future, when you logon, it will use the cached credentials (though it will still complain) to access domain resources.
Now, you also may be experiencing a problem with the Windows browser (not web browser) service. This is what lists computers and shares in the GUI when you map a drive. This system is complex and VERY slow to converge. I wouldn't depend on it if you don't have to. Map shares by explicitly typing in the share name. Batch files can handle this for end users.
There is more but I'm afraid I'm running out of room. If you can be more specific in your question, I may be able to answer better.