Home > IT Answers > Networking > how to prevent Collision in my network
Sirduz
135 pts.
 how to prevent Collision in my network
Network connectivity, Switches
my user sometimes they can't open the data file mapping . but need to log out and login again when they did this they can open the file server. i have 3 switch dell 4 3com all of them are 24 ports i have 1 hub that series the 3 switch, pls answer me cz , iam new here this company.

Software/Hardware used:
ASKED: February 25, 2008  6:10 AM
UPDATED: February 27, 2008  5:58 AM
RELATED QUESTIONS
Answer Wiki:
You'll want to start with removing the hub, and replacing it with a switch. Because you have a hub in the mix you are sending extra traffic to the switches. All traffic between switch 1 and switch 2 is also being sent to switch 3. Hubs are essentailly, "passive" in nature, they transmit traffic to every port on the hub at the same time whether it needs to be transmitted there or not. Therefore, you increase the likely hood that two packets are going to collide. A switch, on the other hand, actually learns where traffic needs to go and sends it to where it needs to go on a port by port basis. What error(s) are your users getting when they can't get the file server open?
Last Wiki Answer Submitted:  February 27, 2008  5:50 am  by  Jerry Lees   5,320 pts.
All Answer Wiki Contributors:  Jerry Lees   5,320 pts. , Denny Cherry   64,520 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

For Sirduz: “Yes Sir Denny.the error for the users is its take longer to open the share folder sometimes its hang so nid to restart the pc to open normally .thanks for the answer . i am very glad to be part of this .:))”

BrentSheets
 6,565 pts.
 

Brent, I have seen situations where it takes a long time to “open” a share to a server that traced back to name resolution issues (either WINS or DNS, but more likely netbiosname resolution)

I wonder is a simple ping to the server name takes an abnormally long time to not only ping— but to resolve. The resolution portion is the first lines of the ping after entering the ping command, it’s a rough estimate but helps as a indicator. In this example it took very little time for the first line to display, essentially 77ms (79ms minus the apparent average of 2ms for the other ping responses)

c:\>ping jlees

Pinging jlees [10.209.209.101] with 32 bytes of data:

Reply from 10.209.209.101: bytes=32 time=79ms TTL=128
Reply from 10.209.209.101: bytes=32 time=2ms TTL=128
Reply from 10.209.209.101: bytes=32 time=2ms TTL=128
Reply from 10.209.209.101: bytes=32 time=2ms TTL=128

Ping statistics for 10.209.209.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 79ms, Average = 21ms

Jerry Lees
 5,320 pts.