SK0-004 · Question #688
A technician receives a report that two users are having difficulty retaining connections to a server hosting a company application. On testing, the technician sees the following: Initial…
The correct answer is A. Two workstations have been configured with the same IP address. Sporadic initial connections, sessions dropping after roughly 30 seconds, and inconsistent reconnects are the classic hallmark of an IP address conflict between two hosts.
Question
A technician receives a report that two users are having difficulty retaining connections to a server hosting a company application. On testing, the technician sees the following:
Initial connections to the server are sporadic.
- If connected, the client is dropped within 30 seconds.
- Attempting to reconnect is sometimes successful but other times requires multiple attempts.
- Local testing on the server reveals no problems.
Given these symptoms, which of the following is the MOST likely cause of the problem?
Options
- ATwo workstations have been configured with the same IP address.
- BTwo separate NICs have the same MAC address.
- CThere are multiple DNS entries for the same host.
- DRouting has been configured incorrectly for the clients.
How the community answered
(26 responses)- A62% (16)
- B23% (6)
- C4% (1)
- D12% (3)
Why each option
Sporadic initial connections, sessions dropping after roughly 30 seconds, and inconsistent reconnects are the classic hallmark of an IP address conflict between two hosts.
When two devices share the same IP address, ARP resolution alternates unpredictably between them. This causes initial connections to randomly reach the wrong host, active sessions to drop when the ARP cache updates to the other device, and reconnect attempts to succeed only when the cache resolves to the intended server - matching every symptom described.
Duplicate MAC addresses would cause Layer 2 switch instability affecting many hosts broadly, not sporadic timed drops for just two specific users connecting to one server.
Multiple DNS entries typically produce round-robin load balancing with consistent partial failures, not timed session drops and intermittent initial connection refusals.
Misconfigured routing would block connections entirely and consistently for affected clients rather than allowing sessions that establish and then drop after a fixed interval.
Concept tested: IP address conflict symptoms and ARP resolution behavior
Topics
Community Discussion
No community discussion yet for this question.