Site Moved a PC=A MESS
-
Now, Before I get started: WE were not there, We did not tell them it was okay and the Site did not get a hold of us before moving the pc. I am simply wanting to see what everyone else says about this and what you think.
We have a site who decided moving the PC to a different room would be a good idea, They did not call us and have us go on site ( To make sure everything connects back up to the back office file server ) they just moved the pc and ran it back to a switch. We use two networks: one for internet, one to run the point of sales system. They stacked Ip addresses on a single NIC ( Like I said we use 2..) and had the Point of sale ran through what the network tech for this site called " The Admin Switch". We were called to fix it. Not knowing what had happened, or where any of the original wiring wen to: Therefore When The Networking tech and I were on site it was the blind leading the blind. The original switch is in the exact location ( I am told) as it was before. However when We moved the PC back to the original room, Plugged it in to the original switch, we cant ping from the point of sale terminals, nor the file server/PC that runs them. We told him to get the original Team out there that actually moved the PC and have them connect it back to the network ( the PC ).
This has been stressing me out and I dont know what else I can do from this point forward. Went on site and was running around everywhere I could to get this back to working order and I got nowhere. Even the Network tech from the site said it was a "F**King Mess." and that There was nothing more or less we could do. The new manager of the site seems to think we are on the hook to fix this, But what Can I do if I wasn't there nor was I informed?
-
This is called sabotage. Someone broke something by doing something they clearly had no idea how to do. Now they are hiding things from you to keep it from getting fixed. Time to escalate. Let someone know that the Site Manager has overseen damage to the network and that you have no idea what they have done and that they either aren't able to tell you or are unwilling to do so. Communicate to the powers that be. The Site Manager is responsible, so of course he's trying to blame you. It's HIS fault.
You might need to suggest that given the unknown state of things, starting from scratch might be the best way to quickly resolve issues and know what the state of things is and what has been done.
And get it in writing that sites cannot make changes as policy.
-
So this PC has 2 NIC's one to the PoS and the other to the Internet? Are they physical or virtual? I'd document what has been changed, and send it back to the original team to undo what they've done and get the system back up and working.
Once it's working again, formulate a plan to moving this system to where it needs to go.
It sounds like you're using physical NICs, can you tone the ethernet out and see where it goes?
-
@dustinb3403 said in Site Moved a PC=A MESS:
So this PC has 2 NIC's one to the PoS and the other to the Internet? Are they physical or virtual? I'd document what has been changed, and send it back to the original team to undo what they've done and get the system back up and working.
Once it's working again, formulate a plan to moving this system to where it needs to go.
It sounds like you're using physical NICs, can you tone the ethernet out and see where it goes?
2 Physical NIC's- We did use a toner to try and see where they went, We actually got a few "hits" ( as the Network Tech called it) but was still unable to Ping that PoS that was giving the tone.
-
@scottalanmiller said in Site Moved a PC=A MESS:
This is called sabotage. Someone broke something by doing something they clearly had no idea how to do. Now they are hiding things from you to keep it from getting fixed. Time to escalate. Let someone know that the Site Manager has overseen damage to the network and that you have no idea what they have done and that they either aren't able to tell you or are unwilling to do so. Communicate to the powers that be. The Site Manager is responsible, so of course he's trying to blame you. It's HIS fault.
You might need to suggest that given the unknown state of things, starting from scratch might be the best way to quickly resolve issues and know what the state of things is and what has been done.
And get it in writing that sites cannot make changes as policy.
My suggestion was to run new Cables to eat PoS Terminal and go from there. The network tech told him to get the team that moved it back out there - because was not either of our companies that made the move.
Everything has been documented, I may need to just escalate this some more. -
@wrcombs said in Site Moved a PC=A MESS:
2 Physical NIC's- We did use a toner to try and see where they went, We actually got a few "hits" ( as the Network Tech called it) but was still unable to Ping that PoS that was giving the tone.
So I assume that the network has no labeling.
Are you able to use a cable tester (just checking pairs) and see if any of the "hits" are the actual cable you're connected too?
If the port is off, unplugging it from the patch panel or switch isn't going to cause any harm for 15 minutes.
-
@dustinb3403 said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
2 Physical NIC's- We did use a toner to try and see where they went, We actually got a few "hits" ( as the Network Tech called it) but was still unable to Ping that PoS that was giving the tone.
So I assume that the network has no labeling.
We did label the NIC's- But no other labeling was done.
Are you able to use a cable tester (just checking pairs) and see if any of the "hits" are the actual cable you're connected too?
My cable tester will not test through a switch ( at least when i tried it that was what I was told).
If the port is off, unplugging it from the patch panel or switch isn't going to cause any harm for 15 minutes.
We also tried it by plugging into the cord at the switch, and trying to tone out to the terminal itself. the Tech told me He got a hit off of that.I might also add that the set up the network for the PoS to be .3 Sub net ( I use Sub net because of the Network tech- thats how he referred to them)
where as the back office had stacked Ip's had sub nets of .2 and .128
Which was not done by us nor did we know of the changes. -
@wrcombs said in Site Moved a PC=A MESS:
@scottalanmiller said in Site Moved a PC=A MESS:
This is called sabotage. Someone broke something by doing something they clearly had no idea how to do. Now they are hiding things from you to keep it from getting fixed. Time to escalate. Let someone know that the Site Manager has overseen damage to the network and that you have no idea what they have done and that they either aren't able to tell you or are unwilling to do so. Communicate to the powers that be. The Site Manager is responsible, so of course he's trying to blame you. It's HIS fault.
You might need to suggest that given the unknown state of things, starting from scratch might be the best way to quickly resolve issues and know what the state of things is and what has been done.
And get it in writing that sites cannot make changes as policy.
My suggestion was to run new Cables to eat PoS Terminal and go from there.
This seems like overkill, you know the cable works, you just don't know where it's connected to. Using a pair* tester would identify the cable, quickly and easily.
A lot of different toners include this functionality to make sure that the (normally patch) cable is in good working order and without crossed pairs.
-
@dustinb3403 said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
@scottalanmiller said in Site Moved a PC=A MESS:
This is called sabotage. Someone broke something by doing something they clearly had no idea how to do. Now they are hiding things from you to keep it from getting fixed. Time to escalate. Let someone know that the Site Manager has overseen damage to the network and that you have no idea what they have done and that they either aren't able to tell you or are unwilling to do so. Communicate to the powers that be. The Site Manager is responsible, so of course he's trying to blame you. It's HIS fault.
You might need to suggest that given the unknown state of things, starting from scratch might be the best way to quickly resolve issues and know what the state of things is and what has been done.
And get it in writing that sites cannot make changes as policy.
My suggestion was to run new Cables to eat PoS Terminal and go from there.
This seems like overkill, you know the cable works, you just don't know where it's connected to. Using a paid tester would identify the cable, quickly and easily.
A lot of different toners include this functionality to make sure that the (normally patch) cable is in good working order and without crossed pairs.
Wanted to be sure, I suppose, You are right though.
-
@wrcombs said in Site Moved a PC=A MESS:
My cable tester will not test through a switch ( at least when i tried it that was what I was told).
But you should be able to just connect it to a PC, while someone watches the switch and see which port lights up or turns off.
Repeatedly connect and disconnect to help identify the switch and port.
-
Repeatedly connect and disconnect to help identify the switch and port.
We tried this
-
@wrcombs said in Site Moved a PC=A MESS:
@scottalanmiller said in Site Moved a PC=A MESS:
This is called sabotage. Someone broke something by doing something they clearly had no idea how to do. Now they are hiding things from you to keep it from getting fixed. Time to escalate. Let someone know that the Site Manager has overseen damage to the network and that you have no idea what they have done and that they either aren't able to tell you or are unwilling to do so. Communicate to the powers that be. The Site Manager is responsible, so of course he's trying to blame you. It's HIS fault.
You might need to suggest that given the unknown state of things, starting from scratch might be the best way to quickly resolve issues and know what the state of things is and what has been done.
And get it in writing that sites cannot make changes as policy.
My suggestion was to run new Cables to eat PoS Terminal and go from there. The network tech told him to get the team that moved it back out there - because was not either of our companies that made the move.
Everything has been documented, I may need to just escalate this some more.What company did it? And why is the site manager allowing random, third party companies to touch stuff?
-
@wrcombs said in Site Moved a PC=A MESS:
@dustinb3403 said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
2 Physical NIC's- We did use a toner to try and see where they went, We actually got a few "hits" ( as the Network Tech called it) but was still unable to Ping that PoS that was giving the tone.
So I assume that the network has no labeling.
We did label the NIC's- But no other labeling was done.
Are you able to use a cable tester (just checking pairs) and see if any of the "hits" are the actual cable you're connected too?
My cable tester will not test through a switch ( at least when i tried it that was what I was told).
By definition a cable tester cannot do that.
-
@wrcombs said in Site Moved a PC=A MESS:
Repeatedly connect and disconnect to help identify the switch and port.
We tried this
And the switches don't have any logging to help identify this activity?
-
@dustinb3403 said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
My cable tester will not test through a switch ( at least when i tried it that was what I was told).
But you should be able to just connect it to a PC, while someone watches the switch and see which port lights up or turns off.
Repeatedly connect and disconnect to help identify the switch and port.
This is what you do when you don't have equipment.
-
@scottalanmiller said in Site Moved a PC=A MESS:
@dustinb3403 said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
My cable tester will not test through a switch ( at least when i tried it that was what I was told).
But you should be able to just connect it to a PC, while someone watches the switch and see which port lights up or turns off.
Repeatedly connect and disconnect to help identify the switch and port.
This is what you do when you don't have equipment.
Or when you're dealing with a rats nest of cabling. .
-
Cable tester, now just imagine the cable goes into a wall and out of a patch panel.
-
@scottalanmiller said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
@scottalanmiller said in Site Moved a PC=A MESS:
This is called sabotage. Someone broke something by doing something they clearly had no idea how to do. Now they are hiding things from you to keep it from getting fixed. Time to escalate. Let someone know that the Site Manager has overseen damage to the network and that you have no idea what they have done and that they either aren't able to tell you or are unwilling to do so. Communicate to the powers that be. The Site Manager is responsible, so of course he's trying to blame you. It's HIS fault.
You might need to suggest that given the unknown state of things, starting from scratch might be the best way to quickly resolve issues and know what the state of things is and what has been done.
And get it in writing that sites cannot make changes as policy.
My suggestion was to run new Cables to eat PoS Terminal and go from there. The network tech told him to get the team that moved it back out there - because was not either of our companies that made the move.
Everything has been documented, I may need to just escalate this some more.What company did it? And why is the site manager allowing random, third party companies to touch stuff?
Another Vendor said " I think this is how this goes so I will Do it." and he allowed them too; this is the new Site manager- the one who allowed them to move it is no longer with the site.
-
@wrcombs said in Site Moved a PC=A MESS:
@scottalanmiller said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
@scottalanmiller said in Site Moved a PC=A MESS:
This is called sabotage. Someone broke something by doing something they clearly had no idea how to do. Now they are hiding things from you to keep it from getting fixed. Time to escalate. Let someone know that the Site Manager has overseen damage to the network and that you have no idea what they have done and that they either aren't able to tell you or are unwilling to do so. Communicate to the powers that be. The Site Manager is responsible, so of course he's trying to blame you. It's HIS fault.
You might need to suggest that given the unknown state of things, starting from scratch might be the best way to quickly resolve issues and know what the state of things is and what has been done.
And get it in writing that sites cannot make changes as policy.
My suggestion was to run new Cables to eat PoS Terminal and go from there. The network tech told him to get the team that moved it back out there - because was not either of our companies that made the move.
Everything has been documented, I may need to just escalate this some more.What company did it? And why is the site manager allowing random, third party companies to touch stuff?
Another Vendor said " I think this is how this goes so I will Do it." and he allowed them too; this is the new Site manager- the one who allowed them to move it is no longer with the site.
Oh okay, so the scape goat has run away.
-
@scottalanmiller said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
@scottalanmiller said in Site Moved a PC=A MESS:
@wrcombs said in Site Moved a PC=A MESS:
@scottalanmiller said in Site Moved a PC=A MESS:
This is called sabotage. Someone broke something by doing something they clearly had no idea how to do. Now they are hiding things from you to keep it from getting fixed. Time to escalate. Let someone know that the Site Manager has overseen damage to the network and that you have no idea what they have done and that they either aren't able to tell you or are unwilling to do so. Communicate to the powers that be. The Site Manager is responsible, so of course he's trying to blame you. It's HIS fault.
You might need to suggest that given the unknown state of things, starting from scratch might be the best way to quickly resolve issues and know what the state of things is and what has been done.
And get it in writing that sites cannot make changes as policy.
My suggestion was to run new Cables to eat PoS Terminal and go from there. The network tech told him to get the team that moved it back out there - because was not either of our companies that made the move.
Everything has been documented, I may need to just escalate this some more.What company did it? And why is the site manager allowing random, third party companies to touch stuff?
Another Vendor said " I think this is how this goes so I will Do it." and he allowed them too; this is the new Site manager- the one who allowed them to move it is no longer with the site.
Oh okay, so the scape goat has run away.
Yes.
