Hello,
Yep, I too have exactly the same problem.
I'm using Vista Enterprise and ISA Server 2006 to connect to my work
network. I have the ISA Client for Vista installed, but cannot connect to
any Network shares.
What I want to do is to be able to sync once connected so that I can work
online and update files that I change from home, like I use to do with
Windows XP! I'm the IT Director, and at present cannot connect when away
from my desk, so this is causing me considerable problems.
My observations to date:
I have noticed that when I first connect I can resolve host names, so from a
command prompt I type "ping hostname", for about 30-60 seconds I can continue
to try and ping resources with success. After 60 seconds name resolution
become unavailable and I have to type the IP address in to ping the host.
NetBIOS is disabled throughout our organisation, by design, via DHCP. I
have noticed that at the time when name resolution disappears, my home
connections starts "identifying" and then goes into "public" mode for a while
before returning to the "private" home mode. Once everything has settled
down the VPN connection seems to identify that it is connected to my managed
corporate network. One would think at this stage that Vista was smart enough
to know that it was connected to my work network and go online, allowing me
to access the resources that should be available. This is not the case.
Strangely, I cannot connect my home PC, running Vista Ultimate, to work via
VPN at all, it hangs at the authenticating username and password stage.
However, I can connect that same PC to another VPN host running ISA Server
2000. I find this very confusing, as some TechNet articles I have read
suggest this should be the other way round.
This is just one of the problems my department has discovered with Windows
Vista.
We are also trying to identify the supposed benefits of the new Windows
Deployment Services. This seems to be more work than RIS ever was, as you
have to visit the client, then go back to the WDS MMC and approved and name
the PC, then return to the client to press F12, by which time it’s probably
timed out. At least with RIS I could name the PC whilst at the physical
machine and then leave it to do an unattended installation.
Also, don't get me started on the deployment of a customised installation of
Office 2007 via Group Policy, because you can't! TechNet says so...
However, I'm "Confident" that everything will become "Clear" once I get
"Connected".