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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Accesing internet via a second Nic on server

Status
Not open for further replies.

jmartin

MIS
Aug 31, 1999
68
PE
Hi,
I added a second nic on netware 4.12 server. both uses ip protocol, the problem begins when a pc attached (via a 3com switch)from the new second nic try to access the ip address which gain access to internet (192.168.1.1), this pc belongs to 192.168.2.XXX network while first nic is part of 192.168.1.XXX network. All pcs attached to first nic can access without problems. I guess the problem is inside 'inetcfg' module.Can anyone explain me how to give access for the second nic to obtain that this pc could make ping to 192.168.1.1 and go out internet??? I tried using nat with bad results.
All suggest are welcome...
 
Hi

Make sure that the server in set to Route info and not set to be an END Node in Inetcfg - protocol - tcpip settings.
This should fix it up. Server must be restarted once this change is made - Reinitialize does not work for this...
Be sure you can ping form one segment to another.

Regards

David
 
Hi Spi200.
Now i can ping from one nic to another. When a station logged to one card can ping througth nic´s server to the router but can´t still go to the web.
Can you explain me the exacts steps for accesing the web via the second nic?
Thanks.
 
Thanks for your ads, but i would like a more detailed explanion about this. I feel some confuse when making changes..Could you tell me step by step?
Thanks
 
Wait a second jmartin, are you using NetWare/IP on the Netware 4.1x OS? This would be the only way you could attach to a NetWare server using the IP protocol. NetWare 4.x and below only support NCP on the IPX protocol.

The suggestion from cmptrnerd is only usefull if you are trying to access a service being hosted by the box doing the NAT. You are using a NAT (I know this because your IP address is a reserved subnet for internsal networks, Internet routers drop packets from these subnets), but it is not your NetWare box. When you did enable NAT, you double NATed your network and thats just a bad thing to do with out proper planning. What you want is routing and you are correct, the solution is in the INETCFG utiltiy.

Users on the 192.168.1.x subnet can get to the Internet because they are not touching the server at all. You will ntoice that your server's IP address on the 192.168.1.x subnet is NOT the .1 node. The 192.168.1.1 IP address is more than likely a DSL router provided by your ISP and has NAT enabled or it could be an Internet appliance that protects your network and provides NAT and maybe DHCP.

To get the 192.168.2.x subnet to gain access to the Internet, go into Inetcfg and choose the Protocol menu opion. Then choose the IP protocol. In the IP protocol, go to the route section and enter in three new routes. It may already be there, but if not put it in. You need a default route in the server to point to 192.168.1.1 Then on your workstations make their Default Gateway the 192.168.2.x address that is on the second NIC in your server. The 192.168.2.x subnet doesn't know how to get to the Internet, but the server does. SO all the workstations must send thier data to the servers IP address so the server can route the packet to the 192.168.1.1 address. Because 192.168.1.1 is on a different subnet, the 192.168.2.x subnet has no idea how to get there. SO you can not use the 192.168.1.1 address as your default gateway on the PC that sit on the 192.168.2.x network.

You also should enter in two routes to make sure both networks can talk to eachother through the server with out issue and return Internet traffic will go to the right subnet. One route would send all traffic for the 192.168.1.0 subnet to the 192.168.1.x NIC. The same goes for the 192.168.2.x subnet. Brent Schmidt CNE, Network +
Senior Network Engineer
provogeek@hotmail.com
East Bay, California; USA
 
Hi Probogeek!
Hope your fix be the solution.
In other words all parameters must be under -protocols -tcpip - route settings?? No need to go to other place in inetcfg.nlm?
Do i need put the ´set NAT dynamic mode to pass THRU = on´?? As say a member here below?
I remember there was a ´public´ and ´private´ ip field, do I need to modify this??
Thanks!

 
Answered in the order asked:

To just setup the routes, yes

You shouldn't need to

No need for NAT or NAT commands

The member recomendation was actualy incorrect for your application

You don't need to do NAT, public and private IP does not need to be modified.




Brent Schmidt CNE, Network +
Senior Network Engineer
provogeek@hotmail.com
East Bay, California; USA
 
Hi Provogeek!
I still having a doubt. In Static route configuration window, what is the value i should put in ´next hop router on route´?? is the nic ip ? or the gateway ip?
Thanks!
 
gateway

Brent Schmidt CNE, Network +
Senior Network Engineer
provogeek@hotmail.com
East Bay, California; USA
 
I feel some confuse...I have my second server nic as 192.168.3.100(and this will be my gateway for terminals) but when i put in the `network field` i receive the message: `Network ip address bits which do not fall within the mask will be truncated IP address 192.168.3.100 will now be 192.168.3.0 ` and i see the terminals can`t surf in internet. The next hope router on route is 192.168.1.1 Is this right? Where is my mistake? Or the Nic ip must change to another ip.
Thanks for your answer.
 
Which protocol must bind the ip protocol?? the ethernet_802.2 or ethernet_II ??
 
When i put the routes on routing table what is the correct type? Host or Network ? I try both and the 192.168.2.X subnet can´t see 192.168.1.1 gateway, i guess i am in a mistake! I saw an option that talks about NAT ( inetcfg/bindings/tcpip/expert../Network Address Translation) Do i need to put values here?? Please correct me for this problem..
 
The problem have been resolved!! It was in the router, which blocked surfing out to the web.
Thanks all member for his adds!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top