Get answers from your peers along with millions of IT pros who visit Spiceworks.
Join Now

I just set up a PC in our machine shop to supplement an aging PC on Windows XP so they can run Office on this. I took out a Netgear ProSafe Switch and connected the main network into port one, the legacy PC into port 2 and this new PC into port 3. The legacy PC is talking to the network fine but this new PC keeps pulling a 169 IP address. I've tried 

  • release/renew
  • FlushDns
  • network troubleshooter
  • Forcing the IP/DHCP/DNS setting (static)
  • Uninstalling/Reinstalling the network device.
  • Different Port on the Switch.

Nothing seem to be resolving this. I've never had this issue and I have many of these switches around the office and no issues whatsoever.

Any other suggestions? 


Garak0410
Cayenne
OP
Garak0410

Took a lot of your suggestions added to more trial and error but it seems to be working now. Combination of old, loose cables, the private network for the roll forming machine and isolating it from our network by using two switches. 

These are the days where being a SOLO IT shop has it's frustrations, especially when it ended up being easy. But it happens in the moment, when it is 100 degrees and 58% humidity in that shop and you have 3 people waiting on you for other things inside the office and they have no patience. 

Learn General Networking with this beginner How-to
During my CCNA studies I learned what is actually happening when I sent a traceroute command. This information is not required to use the...
TEST YOUR SMARTS
Which of the following retains the information it's storing when the system power is turned off?
  • GPU
  • RAM
  • CPU
  • ROM
88% of IT pros got this right.

7 Replies

· · ·
Sosipater
Mace
OP
Sosipater

It could be a bad port. If you put the new PC into port 2 does it work?

1
· · ·
Garak0410
Cayenne
OP
Garak0410

Sosipater wrote:

It could be a bad port. If you put the new PC into port 2 does it work?

I've not tried port two but I did try port 3, 4 and 5. I'll go check that now...

0
· · ·
Sosipater
Mace
OP
Sosipater

Either way, I'd troubleshoot the physical layer before moving up the OSI model. Try different ports, wall jacks, network cables, etc.

1
· · ·
Garak0410
Cayenne
OP
Garak0410

Sosipater wrote:

Either way, I'd troubleshoot the physical layer before moving up the OSI model. Try different ports, wall jacks, network cables, etc.

The other ports work fine for the legacy PC but new one still has issues. I'll try a cable. So weird as this was working perfectly in my office when I configured it. 

0
· · ·
craigmcallister
Anaheim
OP
craigmcallister

Dumb question but have you turned off IPv6 on the new PC?

1
· · ·
gjoseph2
Serrano
OP
gjoseph2

Try plugging the new computer into port 2 with the cable that's already plugged into port 2, may be a bad cable you're using.

1
· · ·
Garak0410
Cayenne
OP
Best Answer
Garak0410

Took a lot of your suggestions added to more trial and error but it seems to be working now. Combination of old, loose cables, the private network for the roll forming machine and isolating it from our network by using two switches. 

These are the days where being a SOLO IT shop has it's frustrations, especially when it ended up being easy. But it happens in the moment, when it is 100 degrees and 58% humidity in that shop and you have 3 people waiting on you for other things inside the office and they have no patience. 

1
Oops, something's wrong below.