Can someone explain clearly the do's and don'ts of getting your Securemote clients to be able to browse the network neighborhood. I have mix of dial-up and dsl/cable users throughout the world, and they expect to be able to authenticate and instantly get access to Exchange and browse the network neighborhood, but many of the clients are taking up take up to 20 minutes of connection time before they are able to browse effectively. They can ping and use other standard TCP/IP apps immediately upon authentication to reach internal systems. A couple of clients have then retained the ability to browse and use all windows services upon exiting and returning, but most do not and will take another 20 minutes of connection. All clients are set up on the network internally first and added to the domain. None have any problems downloading topology or authenticating.
Network Environment:
FW-1 v4.1, latest IPSO build
IKE w/ accelerator
NAT - hidden
NT Server 4.0, netbios over TCP/IP
WINS
Clients:
Windows 98, NT, 2000
latest builds of Securemote (not Secureclient)
setup with ISP's DNS servers but corporate (internal) WINS
Thanks,
Jon Speer
