Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Small business network question

Status
Not open for further replies.

DaH00Psta

Technical User
Jul 19, 2004
7
US
Don't know if this is the right forum to post this question, but here goes...
I'm a networking newbie, so I'm learning as I go and I appreciate any help you guys could offer.
I want clients to be able to access my network through VPN and map drives to my fileserver. I'll be working with a total of about 20 individuals total(local & remote vpn).
I've got VPN authenticating to ServerA successfully, but cannot map drives.

Here's my topology -

Internet > Router > Nic1 > ServerA > Nic2 > Switch > ServerB

Nic1 - 192.168.1.150
ServerA - Win 2003 AD/VPN
Nic2 - 10.10.10.150
ServerB - 10.10.10.151 Fileserver

I know I have some issues here besides mapping drives because the local pcs on the 10 subnet side cannot ping pcs on the 192 subnet, but nic1 and nic2 can ping each other and with RRAS I do have routing enabled.
Any suggestions?
First off, are these subnets ok? I'm not sure how to figure out if they will work together. I do plan on setting up another server on the 192subnet for DNS/WINS/DHCP and turn the DHCP off at the router.
Thanks much...
 
Add a route map from one subnet to the other and vice versa.

Also not sure on the makeup of your network but have you thought about putting the switch on the side of the router and allowing your two servers access to the switch? Just curious if that would work better. Then add a route in the router to point one network to the other.

such as

internet>router>switch>server a
switch>server b

What type of router do you have?
 
. Implement DHCP, and DNS on the Windows 2003 server.
Then:

. Either add the second subnet using an additional WINS server; or,

. Create a common network segment for all clients

With Windows native security tools you can prevent users from seeing, or not seeing, any file or other network resource without trying to use IP addresses to handle a network OS security issue.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top