Networking Forums

Networking Forums > Computer Networking > Windows Networking > what do i need to do this? seperating office networks, at least in one direction.

Reply
Thread Tools Display Modes

what do i need to do this? seperating office networks, at least in one direction.

 
 
Kremlar
Guest
Posts: n/a

 
      01-13-2005, 02:06 PM
Sorry for my inexperience, but I'm looking for some basic advice to get
started.

We are looking to add a Terminal Server and file server to our office (let's
call this NETWORK B), but want to be sure that any remote users terminal
serving in cannot see ANYTHING on our existing network (I'll call it NETWORK
A).

I know I could do this with Active Directory user permissions, but I'd
rather do it at the router/hardware level if possible. The catch is that I
need users on our existing network (I'll call it NETWORK A) to be able to
use specific resources on NETWORK B - say start a remote session on Terminal
Server, or maybe dump some large files to the file server.

I'm considering 2 scenarios - either sharing an internet connection between
NETWORK A and NETWORK B, or possibly getting each network a seperate
internet connection.

Assuming I want to share an internet connection, I would imagine a router
attached to the incoming T1 with 2 LAN connections, and rules setup on the
router to allow traffic from NETWORK A (say 192.168.0.x) users to NETWORK B
(say 192.168.1.x), but not vice versa.

Is this possible? If so, what products should I be looking at?

The other option I am considering is dedicated internet connections.
Probably a basic DSL for NETWORK A and a full T1 for NETWORK B. In that
case, the networks would be almost completely seperated. What would bridge
the 2 together? How would that change things?

Again, sorry if I'm asking some very basic questions, but I'm hoping someone
could point me in the right direction.

Thanks!
Mike


 
Reply With Quote
 
 
 
 
Yousuf Khan
Guest
Posts: n/a

 
      01-14-2005, 02:41 AM
Kremlar wrote:
> Sorry for my inexperience, but I'm looking for some basic advice to get
> started.
>
> We are looking to add a Terminal Server and file server to our office (let's
> call this NETWORK B), but want to be sure that any remote users terminal
> serving in cannot see ANYTHING on our existing network (I'll call it NETWORK
> A).


It seems to me that you're thinking too convolutedly. Why not just buy a
couple of NAT routers (assuming this is a fairly small office), and
attach network B to the Internet via one router, and attach network A to
network B via the other router. That way Network A will see everything
in Network B (including its Internet connection), and Network B won't
see anything inside Network A.

Yousuf Khan
 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
802.11 Direction Finding Michael Ruebner Wireless Internet 8 06-01-2007 05:08 PM
RMI works in one direction in VPN Maciej Linux Networking 0 08-31-2006 05:56 PM
Seperating RIS IPs Sahap Windows Networking 2 02-10-2006 05:05 PM
How to connect laptop to both home (workgroup) and office (domain) networks? Philip Herlihy Wireless Networks 10 05-02-2005 02:30 PM
wifi networks knocking off connections in small office =?Utf-8?B?RGFu?= Windows Networking 0 02-07-2005 04:47 AM



1 2 3 4 5 6 7 8 9 10 11