Question : Group Policy and VBS scripts

We have a single Windows 2000 DC single domain.
The rest of the network is WIndows XP, and Windows 2003 server.

We run a vbs script to map drives and printers, etc.

The problem we are having is it takes a minute or 2 for the script to kick in when users logon.
Which causes problems when they go to access their email, the Notes ID is on a network share, and since the vbs script doesn't kick in
right away.

Can this be a network issue?
Can someone guide me on my way?
I'm kind of perplexed why the shares don't show up right away, and sometimes the mappings in the script don't always get applied.
We have to physically map the drives.

Thanks

Answer : Group Policy and VBS scripts

autumn801:
-Is windows 2003 server a standalone server.
-Which server is controlling the DNS?  What are the DNS settings on the NIC card/s of your domain controller?.  Try setting Primary DNS (internal DNS IP) and Secondary DNS (internal DNS IP) on you NIC cards of the server which runs DNS server and use forwarders only as the IP's of the ISP (if you want to use forwarders its up to you).
-Could be a network issue.  Did you try checking in the event logs?
-For a particular user for whom the shares are coming up (in case you are calling the script from the AD).  In the active directory, under the properties of that specific user, remove the path to the script log on, re enter the path of the script and log on again.  What happens?
-Also make sure that the users belong to that group which have access to that script to run.  for example on our domain a teacher was unable to see the mapped drives, when I checked the member of tab in the properties of that user under AD, I found he was not a member of teachers, I simply added him to teachers group and .......all the drives came back!
Hope that helped.
AM