How to access shared workgroup folders remotely from a user on SBS 2003 Domain

Posted on 2011-03-21
Last Modified: 2012-05-11
Heres the scenario.  We have a SBS 2003 with remote users.  We also have a NAS running Windows File Server 2008.  The NAS is not part of the domain, its on its own workgroup, and ofcourse the SBS is on a domain.  While in the office everyone can access the shared folders on the NAS with no problems at all.  When a user takes their laptop home and connects to the SBS 2003 they cannot access the shared folders that live on the NAS (which is on a workgroup, not the domain).  

I know there is a way to make it happen, I just cant recall it at the moment.  Any help would be great.
Question by:jtrabert
  • 8
  • 7
LVL 26

Expert Comment

ID: 35185296
'they cannot access the shared folders'
Just how does it go BANG!?

Access denied?
or drive letters not connecting?

Can they hit \\NASname\Sharedfolder ?
Can they hit \\\SharedFolder or whatever the IP address of the NAS is?

Can they PING or whatever the IP address of the NAS is?

Is everyone SOL or can admins access stuff?

How is it failing?


Author Comment

ID: 35186064
Thanks for the quick reply.  It works great when everyone is at work.  After re-reading my question I think I should have worded it differently.

At work we have SBS 2003 with a domain called "Company"  all the users connect to the domain.  We also have a NAS running Windows file server 2008.  The NAS isnt on the domain, its on its own workgroup called "Office".  We have all the users access the NAS by mapping a shared drive to it.  So technically they are logging into the NAS through the guest login.  When the salesmen leave for the day and work from home in the evening theylll use their laptops to connect to the domain through VPN.  Now once they are connected to the domain, if they go to their mapped drives they cannot open them.  It'll say the drives are disconnected.
LVL 26

Expert Comment

ID: 35186274
That isn't necessarily insurmountable.  They can execute a login script batch file that will delete / remap their drives manually after connecting if need be.
Can they hit \\NASname\sharedfolder?
If they can, scripting the rest is easy.

Let me know
3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.


Author Comment

ID: 35188963
Ill try it tonight, when I am home from work and remote in.  Ill update the post then, thanks!

Author Comment

ID: 35195580
I just tried it a few minutes ago and I wasnt able to connect to the NAS.

I tried connecting to it through the NAS name and also the IP both didnt work.  It just returns a "The network path was not found".  

When Im connected from home to the work server that conenction is fine, but it wont even let me see the NAS.  Im not sure if I need to set up some kind of link from the server to the NAS since the NAS isnt part of the domain.  
LVL 26

Expert Comment

ID: 35199395

VPNing can be a funny thing.  Depending on how it is set up, the server may dish addresses from DHCP or it can set up it's own range.
The next thing to know is IP addressing.
When you are at work, what IP addresses does your machine, your server and your NAS have?
After you VPNed in, what address does the VPN server give you, and what address does it have?

Can you ping the NAS at work?
open the cmd window
ping NASname <enter>

Then from home, can you ping it?

Author Comment

ID: 35199512
I appreciate all your help so far. The server is set for DHCP (although some PCs have static IPs) and we use a 10.1.10.X scheme.  

At work the server is, NAS is, and laptop is  Now when I go home to test it out the laptop gets its IP address from my home router which is a 192.168.X.X scheme.  Going off of memory Im pretty sure I tried pinging it last night from home and it timed out, but Ill check again tonight.  As for VPN the way we are using it is lauching it from the icon that is  put there from the SBS.  The icon says "Connect to Small Business Server".  

As you can tell, this area isnt my strong point at all.
LVL 26

Expert Comment

ID: 35199628
At home, do an ipconfig /all
You'll be getting a 192.168.x.x from your home server, but you'll also get something from the VPN.
What that is, is of interest if you can't ping the NAS.
I assume you can't ping anything but the server on the network.
But you know what they say about assume...
Ass u me
Ping other stuff besides the NAS when you are at home.
Is it as NAS thing, or as I suspect, an IP/VPN thing

Attached is the server properties page from the Routing and Remote Access MMC.
See if your server is dishing DHCP to VPN clients (good) or from a static pool (boo!, hiss!)

Author Comment

ID: 35199763
Ill check everything out and update this post tonight when Im home from work and can test it, if there is anything else you think I should test at the same time just let me know if not Ill update tonight.  Once again thanks!

Author Comment

ID: 35224410
I was able to test the IP and the setting you posted above.  The settings are as you suggested on the server.  When I did an ipconfig /all here are those settings:

A few things kinda concern me after looking at this info.  The first is that it shows DHCP set to "no", the DNS looks good, but the IP and Gateway are the same, is that normal?  And the Subnet is showing, when it should be if Im correct.

Thanks again for your help.
LVL 26

Expert Comment

ID: 35224713
The spidey sense is tingling.
I recall some remote access connection settings being for "allow access only to this machine" vs "allow access to the network"
Maybe in Remote Access policies?

I'll have to research
Google those strings and see if you come across something.
If I find it first, I'll post back
LVL 26

Expert Comment

ID: 35224780
Another thing to take a swing at is re-running the Internet connection wizard-twice.
Change one minor setting on the first run -- and change it back on the second.
The wizard can be a flakey monster, but it HAS to set the main settings.

I'll keep poking
LVL 26

Accepted Solution

Nick67 earned 500 total points
ID: 35224869
I don't run SBS 2003 anymore.
I moved to an SBS 2008 machine.
The RRAS setup has changed heavily

The default gateway you're getting is the problem -- or a symptom of the problem
It limits access to just the server.
The other settings are ok.

Remote Access policies, or the properties of the VPN.
There's a checkbox in there someplace that is restricting access to just the server.
That's accomplished by assigning that default gateway.
Find that checkbox and you'll be good.

Author Comment

ID: 35278082
Sorry for the delay on getting back to you, I was away on business.  I will double check tonight for those settings.

Author Comment

ID: 35469141
Easy Qlemo, I was out of the country on business.  I just got back on Friday.

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
SBS2K8 ---> 2K12  can I migrate FSMO roles after DHCP -DNS -DATA ? 1 40
slow vpn connection 9 64
CISCO Router 1 29
Use of vpn-filter value  in S2S VPN 2 30
You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' agai…
Let’s list some of the technologies that enable smooth teleworking. 
After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor ( If you're interested in additional methods for monitoring bandwidt…

774 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question