New Vlan = no connectivity

  • This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • November 4, 2013 at 6:36 pm #8047
    nath_e
    Member
    • Total Post: 30
    • Frequent Flyer
    • ★★★

    Hi,

    We have created a new Vlan on a cisco 2960 as we ran out of IP’s. On the new Vlan (10.1.4), the S10 can get an IP address from DHCP on 10.1.3, but then has no access to that vlan. The S10 cannot connect to anything on the 10.1.3 range once is has been given a 10.1.4 address from DHCP. It can’t ping anything, not even the DHCP server it got an ip address from? It can ping other devices on 10.1.4 though.

    The vlan is configured correctly I think as a Mac or a windows laptop can access everything else on 10.1.3.

    Can anyone advise what needs to be added so that the s10 can connection to a different vlan? Are we missing some IP helpers or something? I think it’s something obvious that the terminals need but cannot find the answer anywhere.

    Thanks,
    Nathan

    November 5, 2013 at 8:38 am #24367
    aLiE
    Participant
    • Total Post: 310
    • Jacked into The Matrix
    • ★★★★★★

    you also need to access the FTP servers from your vlan (10.1..4.x)

    November 5, 2013 at 10:40 am #24368
    nath_e
    Member
    • Total Post: 30
    • Frequent Flyer
    • ★★★

    @aLiE wrote:

    you also need to access the FTP servers from your vlan (10.1..4.x)

    other devices can access the FTP server from the vlan, but not the winterms. Do I need to put the ftp server in the switch config somewhere?

    Thanks,

    November 11, 2013 at 8:34 am #24386
    nath_e
    Member
    • Total Post: 30
    • Frequent Flyer
    • ★★★

    Hi,

    Just wondering if anyone has any pointers that might help? Really struggling to find a solution and Wyse wont help as they can’t advise on anything to do with network setup.

    Thanks

    November 11, 2013 at 12:38 pm #24387
    nath_e
    Member
    • Total Post: 30
    • Frequent Flyer
    • ★★★

    Hi,

    I’ve managed to resolve this and thought I’d share the fix.

    On the new DHCP scope for 10.1.4, I had to change the router to 10.1.4.1. It now works fine. It seems really obvious now, but no other device needed a different router to access the network!

  • Author
    Posts
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.