Comware

 View Only
last person joined: 2 days ago 

Expand all | Collapse all

New Procurve, can't access the Internet

This thread has been viewed 0 times
  • 1.  New Procurve, can't access the Internet

    Posted May 28, 2012 08:32 PM

    I added a new procurve 2610 to our current network that has 3 other procurve switches and a firewall/balancer

    New switch 192.168.4.1 (Vlan name "NEWS")

    Existing switch 192.168.2.1 This is the main switch that the others connect to and this switch is connected directly to the firewall.

    Existing switch 192.168.3.1

    Existing switch 192.168.1.1

     

    I can ping and access anything on the other subnets. I can ping the firewall (192.168.2.253)

    I can not ping or access anyrthing on the internet.  I receive the following errror:

    Pinging any-fp3-real.wa1.b.yahoo.com [98.139.183.24] with 32 bytes of data:
    Reply from 192.168.4.1: Destination host unreachable.
    Reply from 192.168.4.1: Destination host unreachable.
    Reply from 192.168.4.1: Destination host unreachable.
    Reply from 192.168.4.1: Destination host unreachable.

    Ping statistics for 98.139.183.24:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

     

    I have attached a copy of the new switch config (192.168.4.1)

    As well as a copy of the 192.168.2.1 config since this is the main switch.

     

    Any help would be greatly appreciated!!!


    #Network
    #VLAN
    #internet

    Attachment(s)

    txt
    192.168.4.1.txt   703 B 1 version
    txt
    192.168.2.1.txt   703 B 1 version


  • 2.  RE: New Procurve, can't access the Internet

    Posted May 29, 2012 04:57 AM

    Hi,

     

    so it seems that your firewall blocks your ping. Your DNS gives you the right IP. Did you created the new Subnet in your FW and did u put it to your trustet Subnets?

     



  • 3.  RE: New Procurve, can't access the Internet

    Posted Jun 01, 2012 01:36 PM

    Hello,

     

    I would ensure the new scope/subnet is created and setup on your firewall and dhcp server. Most common mistake is not allowing your new subnet onto your firewall hence blocking the internet. Make sure you can see your other switches. Maybe run sh cdp ne and ensure you can see all the other neighbours. But the fact that you can ping your fw gateway implies that the traffic isn't allowed out onto the net and to look at your firewall first.

     

    Hope this helps!

     

    Cheers