Internal Network Card not respond

RouterOS General
1

My problem that some times i have to unplug and plug cable again of the internal network even if i restart the server still not respond until i unplug the cable
I dont know where the problem and is there any way i can refresh the network card or make it work without need to unplug

2

Hello,

looks like one of the following (but there might be other reasons too I can’t think of):

  1. You are using crossover cable between Router and Server. The servers are not connected to the same Power Source (different grounding?)?
    If so: use unshielded cable for connection or connect the machines to the same grounding and see if problem remains

  2. One of the cards may be broken (server or client), try replacing it.

Since even rebooting the server is no help, there’s no way to “reset” physical connection. You may try to reboot the Router instead. But I doubt that this will bring the eth in the server up again.

It’s also no good practice since a proper installation with working components should not behave this way. Try figuring out why the network goes down, not how to make it go up again.

Regards
Markus

3

Greetings!

Insure you are not using a duplicate IP. Those are the symtoms if you are trying to boot a computer assigned an IP that is already in use. It (the net interface card) won’t come up if it detects a duplicate IP on the net. By unplugging it, it does not detect the duplicate address and will come up.

4

I already checked alll my network cables and its perfect.
The strnage thing that when i monitor card and show 0 activity after that i unplug the network cable and plug it again and its works fine and show the activity

5

Since you are certain all cables are correct, there is either:

  1. a conflict on the net
  2. a hardware failure of the card
  3. a setup/config error

Try booting the server with the card plugged into a hub only. Nothing else connected. Does the ethernet port come up ok? If it comes up ok, then you have a conflict on the net. If it doesn’t, then it is a hardware failure or config error.

Note: The hardware failure could be caused by either an incorrect/corrupt driver, or incompatible hardware as well as mechanical/electrical failure.