Link to home
Create AccountLog in
Windows Networking

Windows Networking

--

Questions

--

Followers

Top Experts

Avatar of davidgeeee
davidgeeee

Can two subnets be connected between two switches?
I have two subnets on a network one connected to a HP switch and one connected to a Netgear switch. Can I get one device on one subnet to talk to another device on the other subnet?

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of Raj-GTRaj-GT🇬🇧

You'll need a router or a layer3 switch for this. What's the model of your switch?

Avatar of davidgeeeedavidgeeee

ASKER

One switch is an HP v1910 and the other is a Netgear GS724T.

So the HP is a layer 3 switch.  Do I need to create a VLAN on the HP switch with the subnet of the Netgear on it or something?

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of Raj-GTRaj-GT🇬🇧

You got it.

1. Enable routing on HP.
2. Create the second VLAN on HP and give it an IP on both VLANs
3. Assign the second VLAN to the port connecting HP to the Netgear
4. Add the route to the first VLAN on Netgear

I have had partial success with this.  I created a VLAN on the HP switch that matches the subnet of the Netgear switch subnet.  I can ping some devices from the HP subnet to the Netgear subnet but not the one I need.  Just typing this make me think of a typo somewhere.  Anyone know what to look for?

Raj-GT thanks for your help.  I have applied vlan 10 (for the 192.168.10.x network) on the HP switch that is on the 192.168.5.x network and made the made 'trunk'.  I created vlan 10 on the Netgear switch, but maybe I don't need to.  Can anyone help, I think I am close.

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


I can ping the vlan 10 port (192.168.10.13) on the HP switch and the HP switches management IP(192.168.10.13) from the Netgear switch but nothing else.

Avatar of Raj-GTRaj-GT🇬🇧

You don't have to create a VLAN on Netgear, just use native/VLAN 0

1. Check the subnet masks of the VLANs on each switch to verify they are correct
2. Check the default routes on the Netgear, it should point to HP's VLAN 10 Interface IP, or add a route to 192.168.5.x valn)
3. You don't have to create a trunk from HP to Netgear, just use untagged VLAN (HP term) on the interface linking the switches.

Port on HP switch that is connected to Netgear Switch set to untagged.  Turned off VLAN 10 on Netgear switch.  Set default gateway on netgear switch to the ip of the VLAN port on the HP.  From the HP switch (on 192.168.5.x) I can ping the device I need to telnet to on 192.168.10.50.  I cannot ping it from a computer on the 192.168.5.0 subnet.  Truly scratching my head now...

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of pgstephanpgstephan🇦🇺

You need to change the default gateway on that computer on the 192.168.5.0 to be the VLAN address on the HP switch (it should be 192.168.5.x probably x is .1 or .254).

Avatar of Raj-GTRaj-GT🇬🇧

I posted a comment last night stating the same and it seems to have disappeared!?

You need a route on the computer to get to 192.168.10.50. You can change the default gateway to 192.168.5.x (IP of the HP switch in that subnet) or add a static route via command line..

route add 192.168.10.0 mask 255.255.255.0 192.168.5.x

If that works, you can make the route permanent by adding -p to the above command (just after route)

Thanks.

I won't get a chance to add these changes for a couple hours but thought I'd mention this.  The device at 192.168.10.50 is an IP phone controller.  The computer that needs to get to it on the 192.168.5.x network is a Linux box that tracks phone call length, number etc. and delivers reports to other computers on the 192.168.5.x network.  Just in case it matters.  I tell you all how it goes.  Thanks!

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


User generated imageAre these routes on the HP switch okay?  I remoted into a computer on the 192.168.5.x  network, that is directly connected to the HP switch, added the static route and tried to ping but got not response.  I can still ping from the HP switch to the PBX at 192.168.10.50.

Avatar of Raj-GTRaj-GT🇬🇧

Make sure the IP phone server is not rejecting/dropping ping due to frewall rules. Let's go through the settings and troubleshoot step-by-step (correct me if I've got something wrong here)

HP Switch
Native VLAN: 192.168.5.0
Native VLAN IP: 192.168.5.1
Default Gateway: 192.168.5.5
VLAN 10 IP: 192.168.10.13
Routing Enabled between VLANs

Clients connected to this switch should have an IP on 192.168.5.x range and have 192.168.5.1 as their default gateway. Make sure you remove the static route first and try pinging 192.168.10.13 from a computer connected to this network. If it worked, then ping 192.168.10.x (Netgear's IP) and then the destination you want to reach (IP Phone server).


Netgear
Native VLAN: 192.168.10.0
Native VLAN IP: 192.168.10.x
Default Gateway: 192.168.10.13

Set 192.168.10.13 as the default gateway for clients on this network and ping 192.168.10.13. If it worked, then ping 192.168.5.1 (HPs native VLAN IP) and then move on to ping any other device on the 192.168.5.x subnet.

Double check the settings and follow the checks and let me know.

*** Y- means checked and confirmed


HP Switch
Y-Native VLAN: 192.168.5.0
Y-Native VLAN IP: 192.168.5.1
Y-Default Gateway: 192.168.5.5
Y-VLAN 10 IP: 192.168.10.13
?-Routing Enabled between VLANs
***   Can't find where to enable this

Y-Clients connected to this switch should have an IP on 192.168.5.x range and have 192.168.5.1 as their default gateway.
Yes this works - Make sure you remove the static route first and try pinging 192.168.10.13 from a computer connected to this network.

Y - If it worked, then ping 192.168.10.x (Netgear's IP)

No - and then the destination you want to reach (IP Phone server).
***however I can ping another device on the 192.168.10.x network(192.168.10.55)
     


Netgear
Y-Native VLAN: 192.168.10.0
Y-Native VLAN IP: 192.168.10.x
Y-Default Gateway: 192.168.10.13

***The following I will have to go onsite for later today:
Set 192.168.10.13 as the default gateway for clients on this network and ping 192.168.10.13. If it worked, then ping 192.168.5.1 (HPs native VLAN IP) and then move on to ping any other device on the 192.168.5.x subnet.

Double check the settings and follow the checks and let me know.

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


Avatar of Raj-GTRaj-GT🇬🇧

if you can ping another device on the remote subnet then routing is working as it should between the networks. I would suggest you check the default gateway, firewall or static routes on the phone server.

The default gateway on the phone server is set to 192.168.10.254.  What should it be the netgear switches IP?

I am having the phone guy switch the default gateway to 192.168.10.10.

Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


ASKER CERTIFIED SOLUTION
Avatar of Raj-GTRaj-GT🇬🇧

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account

It just goes to show me at least that you need to verify all the easy stuff first before working on more complex items.

Thanks  Raj-GT!
Windows Networking

Windows Networking

--

Questions

--

Followers

Top Experts

The Windows operating systems have distinct methodologies for designing and implementing networks, and have specific systems to accomplish various networking processes, such as Exchange for email, Sharepoint for shared files and programs, and IIS for delivery of web pages. Microsoft also produces server technologies for networked database use, security and virtualization.