Operating System - HP-UX
1847342 Members
2153 Online
110264 Solutions
New Discussion

Re: Client cannot connect to external network

 
Jon Davis
New Member

Client cannot connect to external network

I have 2 NICS installed in a J6700 running HP-UX 11.00 and acting as an ignite server. The first NIC is connected to a Windows 2000 Server and is able to ping and connect externally. The second NIC is connected to a hub with local clients connected. From the local clients I am able to ping both NICs of the J6700, but am unable to ping the Windows Server (externally).

How do I go about getting the clients to connect beyond the J6700?

This is the output of netstat -rn:

Routing tables
Dest/Netmask Gateway Flags Use Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 2380 lo0 4136
192.168.1.2 192.168.1.2 UH 0 0 lan1 4136
192.168.2.102 192.168.2.102 UH 0 44708 lan0 4136
192.168.2.0 192.168.2.102 U 2 0 lan0 1500
192.168.1.0 192.168.1.2 U 2 0 lan1 1500
127.0.0.0 127.0.0.1 U 0 0 lo0 4136
default 192.168.2.1 UG 0 0 lan0 1500


I have attached a copy of my netconf file

Thanks,
JD
7 REPLIES 7
Steven E. Protter
Exalted Contributor

Re: Client cannot connect to external network

My understanding is trying to have to network cards on the same subnet can cause problems on HP-UX.

Since the network is different, its not like when I tried bringing up two NIC cards on the same subnet and network. That dropped networking to a halt.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Michael Steele_2
Honored Contributor

Re: Client cannot connect to external network

Test for connectivity starts with the second layer, then the third and finally the fourth. For 2nd layer use the MAC address, ip for 3rd, telnet into a socket for the fourth.

2nd layer:

arp -a (* works on both 2000 and HP-UX *)
linkloop MAC (* 'linkloop is a HP-UX command. Use lanscan to find the MAC. Use ipconfig /all on 2000. *)

Check speed and duplex for both NICs.

2000

On 2000 select properties of 'My Network Places' with a right click, then right click again on LAN connection, then locate the NIC under 'Connect Using' and click on configure > Use the Advanced tab and select 'link speed and duplex'. Finally use the drop down menu to change the value, if needed.

HP-UX

lanscan (* note NMID / PPID *)
lanadmin -x NMID/PPID
i.e.,
lanadmin -x 4
Support Fatherhood - Stop Family Law
Michael Steele_2
Honored Contributor

Re: Client cannot connect to external network

Ooops. Here's how you change the NIC speed and duplex on HP-UX.

lanadmin -X 4 100FD (* 100 Mbps @ Full Duplex *)
Also use,
100HD
10FD
10HD
Support Fatherhood - Stop Family Law
Sridhar Bhaskarla
Honored Contributor

Re: Client cannot connect to external network

Hi JD,

Your HP-UX system is a route by default if you didn't change your ndd parameters. Check if you get "2" in the following command.

#ndd -get /dev/ip ip_forwarding

2 means, the ip forwarding is on if the system has more than 1 interface.

Now on the clients, add your system as the router for the other network. For ex., if you want the clients in 192.168.1.0 to connect to 192.168.2.0 network, you would add the route as follows (if they are HP servers, otherwise follow the commands specific to that OS).

#route add net 192.168.2.0 netmask 255.255.255.0 192.168.1.2 1

This way, the clients send packets to 192.168.1.2 (which is your HP system) destined to 192.168.2 network. HP system will forward those packets to the other interface.

If ndd does not return "2", then you need to set it.

ndd -set /dev/ip ip_forwarding 2

(Modify /etc/rc.config.d/nddconf to make it permanent).

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Ron Kinner
Honored Contributor

Re: Client cannot connect to external network

It's not enough to have a route to the window box. The window box has to know how to get back to your local network. You will need to add a route to the window box.

From a command line on the window box(run/cmd) type:

route add 192.168.1.0 mask 255.255.255.0 192.168.2.102 -p

I assumed the window box was 192.168.2.1.

Your hosts have to know that they can get to 192.168.2.0 255.255.255.0 via the HPUX at 192.168.1.2. IF they are trying to go out onto the internet they will need this as their default. I'm not sure how well Internet COnnection Sharing works if the Windows box does not assign the IP addresses but this should at least let you talk to the window box.

IP forwarding is usually on by default on HPUX but if it's not follow Sridhar's advice.

Ron
Jon Davis
New Member

Re: Client cannot connect to external network

Thank you very much Ron and Sri I found your suggestions to be just what we needed. I added the route to the internal hp-ux client as Sri said that then added the route on the windows box as Ron stated and everything works beautifully. I would like to thank you all. I am new to using these forums...how does this points system work? I would like to give both of you guys some credit!
Sridhar Bhaskarla
Honored Contributor

Re: Client cannot connect to external network

Hi JD,

It was in my mind to add the reverse routing on the windows box but finally forgot.

Point system is to determine how much help the answer provided to resolve the issue. This way a person looking at the thread can quickly determine the best answer. If you strictly apply that system, you would be giving me around 5 as I missed the other part. Ron would be getting 7-10.


-Sri
You may be disappointed if you fail, but you are doomed if you don't try