Troubleshooting VLAN access: A new host is connected to a switch but cannot log into the server on the same switch. What is the most likely issue?

Difficulty: Medium

Correct Answer: The switch port the host is connected to is not configured to the correct VLAN membership.

Explanation:


Introduction / Context:
Hosts connected to the same switch must belong to the same VLAN to communicate without routing. Misconfigured VLAN assignment is a common cause of access issues.



Given Data / Assumptions:

  • New host connected to switch port.
  • Cannot communicate with server on same switch.


Concept / Approach:
Switches segment traffic into VLANs. If the host port and server port are not in the same VLAN, frames will not be forwarded between them without an L3 device.



Step-by-Step Solution:

Check VLAN membership on both ports.If mismatched VLAN IDs, host and server cannot see each other.Correct by configuring both ports into the same VLAN.


Verification / Alternative check:
Run show vlan brief to confirm port VLAN assignment.



Why Other Options Are Wrong:

  • A: Router not required if both devices are in same VLAN.
  • B: VTP propagates VLAN info but not per-host config.
  • C: Invalid MAC would prevent switch registration, rare scenario.
  • E: Server NIC issue would affect all connections, not just this host.


Common Pitfalls:
Assuming VTP handles host-specific access; overlooking VLAN port assignment checks.



Final Answer:
The switch port is not configured to the correct VLAN membership.

More Questions from Virtual LANs

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion