@slimbob: i tried swap the cable and it still doesnt work.
@tonerbomb: you mean put a switch between the wall socket and the MFP? i didnt try that yet but if there is no other solution i''l try on that, but sure if there is any impact on their network monitoring software.
@ApeosMan:@q1: no i did not try with cross cable, usually i test the print using straight cable back in my company's workshop
@q2: no timeout when i ping using network. It also responds according when I unplugged and replug the cable as well as restart the machine when I testing for IP conflict.
@q3: yes. that's the only MFP with that particular problem. Original problem is at with MFP B. Interesting to note that when I move the NIC from MFP A to MFP B ,both shows the same issue when I plug it back using respective cable (port) but when I swap the port (now same port is connected to same NIC but different MFP) the problem shows in MFP A and MFP B works just fine. I also switched with another NIC which I tested before, same problem still occurs and the best part is the old NIC function perfectly fine in my company's workshop!
@q4: Not entirely sure. The problem did surface a while ago but they were upgrading their system and check to see if the cable within the walls is responsible. Not sure what they did, but the problem disappear after that (something like coincidence solution
). Now it rises again.
@q5: i didnt check on that. I'll reconfirm at site. I though the MAC address is bind to the NIC card itself. Not sure if its relevant, I did change the main controller unit before though but didn't change the memory chip, i fix back the old one so the setting didn't go away.
@q6: they do have network monitoring system but they didn't put in any form of restriction, just monitoring as per my understanding. Not sure if its relevant, the print server insists that it has 5 held jobs but didnt print any when i somehow manage to get it running. I'm basically stuck with 2 MFP where only 1 of them can print at a time.
Bookmarks