Hi Jim, Access isn't the actual problem, we did consider using the main office credentials for the Branch Office but the main office is a barn in a field literally in the middle of nowhere (dont ask) so were worried that the Branch Office would grind to a halt when power or comms went down at the main office (as it does quite often). So it isn't access but just opening documents on a network

Hi Henrik, I can ping the server IP and FQDN without issue from internally and across the PWAN from the Branch Office, I cannot change the IP address schema now it is all setup because of the PWAN configuration, I am getting very good ping results with hardly any latency both from internal and across the PWAN. This is a workstation IP Config: Workstation IPConfig Ethernet adapter Local

Thanks Lanwench, I was a bit surprised to see the mapped drives and on checking the administrator account saw that it had the SBS login script in the profile - have promptly removed, wondered though if SBS had put it in - need to check other SBS networks. Thanks again "Lanwench [MVP - Exchange]" <lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message news:%%23pL1XlifIHA

TEB <ThickEB@gmail.com> wrote: Hi Lanwench, this is my login script: \\CMCSERVER\Clients\Setup\setup.exe /s CMCSERVER net use y: \\CMCSERVER\data\CMC net use z: \\CMCSERVER\data\fileserver\cmc net use l: \\CMCSERVER\Futurelink I have only tried the net use command from the server and the above are showing as disconnected? You shouldn't be mapping drives on the server at

TEB <ThickEB@gmail.com> wrote: Hi Henrik, I am not getting any errors anywhere, everything was setup via the wizards, I am beginning to wonder if it is a mapped drive issue, all shared data is mapped via login scripts and are used extensively by the users. Type net use in a command prompt & see if there are any drives in a disconnected state or any unavailable shares