Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have our main network windows domain, but we also have some standalone machines that aren't on our domain, we want to setup a separate network, 192.168.2.xxx for the standalone machines to use. We have a storage server 2008 machine setup on both networks, it is a member of our domain. How could I go about making a file share available to computers on the domain as well as on the 192.168.2.xxx network?

Clarification: I currently can't access any windows file shares on the server from the 192.168.2.xxx network. I can ping the server and remote desktop to it. I can access all shares/normal behavior on the domain side. Is there anything I need to do to be able to use the windows shares from the 192.168.2.xxx network?

share|improve this question
    
Are these standalone machines the same physical network? –  Jeff Feb 16 '11 at 19:06
    
Yes, both networks are physical, the server has 4 nics, 2 on the domain and 2 on the "Stand alone". –  Peter Feb 16 '11 at 19:24
add comment

1 Answer

up vote 0 down vote accepted

The normal practice is to create one or more domain accounts to be used for accessing shared resources on domain machines. Users on the non-domain machines (standalone really means they're not on a network) use those accounts to access the shares. The accounts can be locked down as much as you require to prevent them being used for other purposes.

share|improve this answer
    
Ok, thanks for the suggestion. I made the question a little more specific, I currently can't access the server from the 192.168.2.xxx network, do I need any routing statements in the shared sever? –  Peter Feb 16 '11 at 21:59
    
And in response to the "Stand alone comment" these computers are stand alone currently I'm testing an network that I'll connect them to, but I still think of them as standalone because they aren't on the domain. –  Peter Feb 16 '11 at 22:33
    
@Peter, It's worth checking the routing on both server and client but I suspect the firewall on the server may be the culprit, as it would most likely be treating the other network as untrusted. –  John Gardeniers Feb 16 '11 at 22:37
    
I don't know much about routing, I deal mostly with switches. Could you give an example of a route statement that would do something similar? I have the firewall off on the server but I still can't get any to windows shares. –  Peter Feb 17 '11 at 6:15
    
@Peter, as I don't know anything about your network the best I can suggest is to open a cmd window and type route /?. You're going to want to use route add to add the appropriate routes. –  John Gardeniers Feb 17 '11 at 8:33
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.