Question Unable to connect to Local Network after moving the PC in a Enterprise building

[BlackGameNeon]

Hello everyone.

I am in a Enterprise Network, a client PC was connecting to the Local Network with no problems. Computer is outdated (Windows XP) because is running specialized SW.

This PC was moved to another part of the building. After this, it is unable to connect to the Local Network again.

Why this happens?

I like networking and I am willing to learn. If you ELI5 me will be great, if you happen to share me a YouTube video about it will be awesome.

Thank you!

 

[BlackGameNeon]

While I was with the owner (O), these were my procedures:
1. I found out that both the IP and the DNS were fixed. O changed the IP. I asked to change both IP and DNS to automatic. We /release and /renew. In each process we tried; we couldn't.
2. O told me that he has a laptop that doesn't have the issue. I asked if he cable-connects it in that same room. O's answer was Yes.
3. I asked when the issue started; O is convinced that started when he moved the PC.

My conclusion was that the PC doesn't have the privilegies to access the files in the private network; the room is in another floor and building.

There's a trusting issues with the head of the IT Department; I think O tried to solve it without his intervention (this happened today).

Can you qualify my actions? Thanks @Lighting Shade.

 

[socean.]

Is the computer giving a 169 address or no connection at all? I know it’s dated but I’m curious

 

[Garion]

It is likely that the other part of the building is on a different subnet. That means the IP address assigned at the old location won't work there. You said you tried to adjust the computer use to obtain an IP automatically which didn't work. That is likely because the new location doesn't have a DHCP server, which is used to assign IP's automatically.

DHCP is common for networks that users use, but in many special segments, (i.e. data center servers, networks meant to be used for specialized endpoints like machines, etc. ) DHCP isn't available - They don't WANT people to plug in and use those networks. If you HAD to get on the new network you would need to get an IP address assigned to the computer. Since it sounds like the IT department isn't part of this plan, that's probably not going to happen.

It is *not* a good idea to randomly choose an IP address on a network and just use it - You might end up picking an address already being used by something important and breaking it - don't be That Guy who accidentally takes down the file server and breaks everyone else.

- G

 

[BlackGameNeon]

Thanks for your reply.

I ended up leaving that job. They had a tech mess.

don't be That Guy

I'll try not to be, great suggestion 👍

Have a great one everyone.

 

[Fallen Kell]

Well, good to know that you left. Lots of red flags all over that issue. My first guess would have been the head of the IT department had proper network security enabled and had something like "port security" on which if you move a computer to a new network port than the one it was on, the new port will get disabled (since the device is not authorized until they update the configuration in the switch to tell it that the MAC address is good). It will also disable the original port that the computer was previously connected into if all the switches are properly setup.

For a hint as to why you do this, it is to prevent someone who gained entrance into the building from unplugging a system/printer/phone and plugging in their own device.