• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 761
  • Last Modified:

RHEL 5.6 Network adapter configuration problem (unique)

I installed RHEL 5.6 on my system.  I am trying to configure the network adapter

I configured the network adapter through XWindows using
the following procedure:

    - Select DNS tab, enter the following:

      Hostname:         h_one
      Primary DNS:      10.14.10.10
      DNS Search path:  xxx.xxx.com  (Cant reveal this, but
                                      it always works in 
                                      previous installations)

    - Select Devices Tab, Choose your ethernet adapter, and
                      enter the following:
      Address:          10.14.50.12
      Subnet Mask:      255.255.0.0
      Default Gateway:  10.14.10.10

Open in new window


Then I deactivate and activate the adapter.  It comes up
correctly as active.

Then I CAN ping the adapter:from within the RHEL server terminal on XWindows:

ping 10.14.50.12
PING 10.14.50.12 (10.14.50.12) 56(84) bytes of data
64 bytes from 10.14.50.12: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 10.14.50.12: icmp_seq=2 ttl=64 time=0.027 ms

Open in new window


Then I ping the DNS, but can not get to it

ping 10.14.10.10
connect: Network is unreachable

Open in new window

Nor can I get to common addresses on my network:

ping 10.14.100.2
connect: Network is unreachable

Open in new window


From my clients, I try to ping the new server, but get the following:

ping 10.14.50.12
Pinging 10.14.50.12 with 32 bytes of data:
Request timed out.

Open in new window


Can anyone give me any advice on this.  What seems to be the problem ?
0
Los Angeles1
Asked:
Los Angeles1
  • 2
  • 2
  • 2
1 Solution
 
jackiechen858Commented:
Default Gateway:  10.14.10.10

Are you sure the default gateway is correct?

If the gateway ip is correct, then try to change the cable.
0
 
Los Angeles1Author Commented:
The default gateway is correct
0
 
jackiechen858Commented:
from a console, run "ifconfig" and post the result.
0
Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

 
woolmilkporcCommented:
Are you sure that the other machines and the gateway use the same netmask 255.255.0.0?

wmp
0
 
Los Angeles1Author Commented:
The ifconfig did the trick.  I had transposed the mask and the gateway values

I can not ping out of the box, and can also putty in

Thanks
0
 
woolmilkporcCommented:
So the mask was the culprit?
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now