Solved

Computer lab can not access the internet.

Posted on 2004-10-10
8
304 Views
Last Modified: 2010-04-10
I have a network that uses 10.0.0.x for computers in a lab environment and 192.168.0.x for all of the internal employees. The 10.0.0.x computers can ping any of the 192.168.0.x computers except for the gateway which is 192.168.0.1. I wan to get these 10.0.0.x computers onto the internet but because they can not ping the gateway I can not get them onto the internet. Any suggestions on how I can get these computers to see the gateway and get them out to the internet. Thanks.
0
Comment
Question by:jmoody
  • 3
  • 2
  • 2
  • +1
8 Comments
 
LVL 12

Expert Comment

by:aindelicato
ID: 12273967
Please provde your LAN Layout.

Internet Source

Routers (with IPs)
Firewalls
Switches
Hubs


If you dont have a switch which supports VLANs , you can use a setup similar to this:

                                                                  |--- LAN Computers for 192.168.0.x
ROUTER 1 (WAN/ISP  LAN/192.168.0.1) --|SWITCH|
                                                                  |--- ROUTER 2 (WAN/192.168.0.2  LAN/10.0.0.x)
                                                                             |
                                                                             |--LAN Computers for LAB 10.0.0.x

0
 

Author Comment

by:jmoody
ID: 12274284
There is one router connecting to the internet and that is the 192.168.0.1. It is also the Firewall. Our switch does not support VLANs. We have a Windows NT 4.0 Server with two NIC’s that serve out the IP’s for the two networks via DHCP. Currently the 10.0.0.x computers use the server as a Proxy to get out to the Internet but it is under a heavy work load and the web and proxy services keep failing. I was able to by-pass the server and use the 192.168.0.1 as the gateway for the 192.168.0.x PCs but not the 10.0.0.x PC’s. Hopefully the diagram below makes some sense.


                                        SWITCH --------- to 192.168.0.x PCs    
                                         |
         192.168.0.x ---------| |
SERVER|----------------SWITCH--------ROUTER 192.168.0.1 ----------- INTERNET
         10.0.0.x -------------| |
                                         |
                               SWTICH ------ to LAB 10.0.0.x
0
 
LVL 12

Expert Comment

by:hkunnana
ID: 12274972
You can bypass the server for the 192.168.1.xx pcs because they are in the same IP range with the gateway, hence they can reach it. On the other hand, pc's in the range 10.0.0.x cannot see the gateway because it in different subnet.
What you need is to make the 10.0.0.x pc see the router 192.168.0.1

either
1-change (or add another) ip of the 10.0.0.x to be in same subnet as the 192.168.0.x
2- add another ip to router (sub-interface) in the range 10.0.0.x and define it as the gateway for the 10.0.0.x machines.

3- have another machine (or router device ) connect the two subnets (because directly the two subnets CANNOT see each other).
0
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.

 

Author Comment

by:jmoody
ID: 12275392
The server is acting as a router as the two subnets can see eachother. But right now the 10.0.0.x can ping any of the 192.168.0.x PCs but can not ping the gateway at 192.168.0.1. Why is this?
0
 
LVL 12

Expert Comment

by:hkunnana
ID: 12275545
This is because the router itself doesn't know about the network 10.0.0.x  .
The ping command needs the both parties can reach each other ( If you try to ping any of the 10.0.0.x from ther router, it will fail)
You will need to define a static routing in the router to tell it ( in order to reach the network 10.0.0.x you will need to go through the gateway address <address of the NT server in the 192.168.0.x range>)

I don't know which type of router you have, so you will need to add the static routing command to the router "according to it's os" as follows


Network-to-reach   mask           go-through            
10.0.0.0                 255.0.0.0  192.168.0.serverIP

0
 

Expert Comment

by:cairnsfuture
ID: 12275553
do a route print and post, also do a tracert 192.168.0.1 at the command prompt on a workstation on the 192.168.0.x series and see were it is going.
0
 
LVL 12

Assisted Solution

by:hkunnana
hkunnana earned 100 total points
ID: 12275558
I would like to add, this will still impact on the performance of the NT server (as it will act as a router).
The better solution is to define another IP on the routers ethernet interface in the range of 10.0.0.x and define it as the gateway for the machines in the 10.0.0.x range
0
 
LVL 12

Accepted Solution

by:
aindelicato earned 400 total points
ID: 12280772
The (2) NIC approach is out dated and rarely used as routers and switches with VLAN capabilities are relatively inexpensive.

You can use a simple Linksys cable/DSL router to achieve the second subnet as listed in my diagram above.

That Linksys router will server DHCP addresses in the 10.0.0.x subnet while it's WAN port is that of a 192.168.0.x.  All internet traffic for 10.0.0.x will be natted thru that 192.168.0.x IP.

0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Question has a verified solution.

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

Suggested Solutions

Data center, now-a-days, is referred as the home of all the advanced technologies. In-fact, most of the businesses are now establishing their entire organizational structure around the IT capabilities.
When it comes to security, there are always trade-offs between security and convenience/ease of administration. This article examines some of the main pros and cons of using key authentication vs password authentication for hosting an SFTP server.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

856 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