Home > other >  H3C across a network segment communication problems
H3C across a network segment communication problems

Time:11-25

Good bosses, currently a cross segment communication problems

There are two in the use of network segment 192.1.1. * and 192.1.2. * a is used to the wired network, one is to use wireless network, routing, switches, AC is used both for equipment, there is no isolation, AC
Recently in 192.1.1. * added a server, a network segment 192.1.1.4 but in 192.1.2. Unable to ping to 192.1.1.4 * wireless equipment, at the same time 192.1.2. * device can ping to 192.1.1.2 and 192.1.1.3 add server before, at the same time, 192.1.2.1 wireless network gateway can ping to 192.1.1.4 routing, but in front of the switchboard 192.1.0.1 can ping to 192.1.1.2 and 192.1.1.3 add server before, but he couldn't ping 192.1.1.4

Could you tell me if you want to make wireless networks equipment ping to 192.1.1.4 whether need to change the routing tables in the routing?

CodePudding user response:

Directly see the server's firewall policy, since 2 segment please explain routing to 1 segment before server itself is no problem,
Tracert - d routed tracking to see where the impassability, server the ping of 2 IP to see whether can pass, ICMP impassability back and forth is the ACL, routing, firewall a few questions

CodePudding user response:

A map or draw a topology,

CodePudding user response:

reference 1/f, ice cream, jelly and response:
directly see the firewall policy of the server, since 2 segment please explain routing to 1 segment before server itself is no problem,
Tracert - d routed tracking to see where the impassability, the server of the ping 2 IP to see whether can pass, ICMP impassability back and forth is the ACL, routing, firewall a few questions
and it's been amazing though ping, but remote desktop can be connected

CodePudding user response:

Study any more, I also is often broken network

CodePudding user response:

Can remote desktop can't ping, is a firewall ban ping

CodePudding user response:

butter jelly ice reference 5 floor response:
can remote desktop can't ping, is a firewall ban ping now


There should be no, there are two IP is server before, can ping before, but after retirement, new services for the two IP, wireless or ping impassability, during a firewall didn't change the rules,

And our configuration is routing - "firewall -" behavior management - "switch, switch it now can ping new cable IP
  • Related