Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[freewoman]

Early Thursday morning, my workplace had an electrical outage.  When I got to work, not only did I find out about the power being out, but I had the following message on my computer:  "The system has detected a conflict for IP address ___.__.__.__ with the system having hardware address __:__:__:__:__:__.  The interface has been disabled."  Obviously the computer (a crappy Compaq with--God help me--Windows ME on it) cut off my connection to the DSL line.  Is there any way I can get this back without calling a pro in to help?  We have Verizon DSL, if that makes any difference.  Thanks for any help y'all can provide;  this is way over my head, tech-wise.

[Lenny]

A reboot is likely to do it. The DSL router gives each computer an address, and the error message means that it gave your computer's address to someone else. Rebooting should cause it to get a new address, and all should be well.

[Ire]

The device has been modified.

[freewoman]

I rebooted several times, with no results.  Any other ideas?

[lee n. field]

Reboot.  It should pick up a different address from the DHCP server.

Or, start, run, "cmd", type "ipconfig /release"press enter, type "ipconfig /renew" press enter.

[Lenny]

It sometimes helps to reboot the router, too. It will forget the addresses it gave out and start over.

[Iconoclast]

You all are assuming that her office network is setup using DHCP. It's possible that the network admins are using static IPs, in which case rebooting until the cows come home will do no good. If this is the case and someone hijacked your IP Address, you have two options... find the rogue system and remove it from the network (turn it off... or my favorite is to cut the cat5 cable) or change your workstation's IP address yourself... and hope that you choose an address that is not in use by another system.  If you choose this route, choose a higher number in your subnet range (the last octet and usually between 1 and 254, assuming a flat class-C internal network) and reboot the system. You can keep doing this until you find an unused IP address.  I've never used ME, but I think the IP config utility is something like Device Manger --> network --> <interface> --> IP configuration (If someone knows ME, maybe they can help out here)  This is also one way to see if you have a static IP address or are setup to use DHCP.  If you take this route, you will have to notify Tech Support sometime soon and have them officially assign you a new IP address and/or slap the wrists of the person who hijacked your IP address.  Good luck!

[freewoman]

Thanks for the suggestions, y'all!  I'll give them a try tomorrow.

[khagler]

The next time you see the conflict message, you should write down the "hardware address" part. Your IT guys should be able to identify the offending system from that.

[ZooT_aLLures]

Yeah.....that'll be the MAC address of the offending network card......and it's hardcoded into the card.....

[freewoman]

I wrote down the hardware address already, so I'm set to go.  Unfortunately my computer is no longer supported by tech support; I'll have to hire someone to fix it!  My boss keeps saying I'm getting another computer soon.  Which would be good, except that I've switched computers 3 times already.  Transferring files is a PITA. 

[lee n. field]

Unfortunately my computer is no longer supported by tech support; I'll have to hire someone to fix it!

Bullshit.  It's a networking issue.  This should be relatively easy to fix.

On you desktop, right click Network Neighborhood (or whatever it's called in ME).  Click properties.  Click TCP/IP (whichever one is bound to a lan adapter, not dialup).  click properties.  Look at the address.  If it is set static, not automatic, change the last number to something else, within the range of 2 to 254.  Click OK.  ME will want you to reboot.  Keep doing this until you get an address that is unique on your network.

 I'm surprised, BTW, that you have an ME machine.  ME was never anything but a home user OS, and a particularly loathed one at that.  It's shortcomings were many, and it's sole advantage over Win98 was having USB storage drivers.  A Presario 5000 by chance?

[Iconoclast]

Bullshit.  It's a networking issue.  This should be relatively easy to fix.

What he said! 

This appears to be a networking issue, not a hardware issue with the computer, so the IT guys should take a look.  Worst case is that your network card is just flakey.  They should be able to tell you if this is the case.  If it is, go out and buy a $10 netgear network card (Staples, Best Buy, NewEgg, etc.) and install it in the system. Maybe you'll have to load the drivers for the card... then configure it for the network.... a lot cheaper than paying someone else to do it.  If you are working for the man, why would YOU have to pay for their computer to be repaired?  Or did I misunderstand?  If you have any say in the matter, why not scrap ME and load Linux (Ubuntu/Kubuntu?)  You could always install WINE and then install your MS Office Apps, for work compliance.

Yeah.....that'll be the MAC address of the offending network card......and it's hardcoded into the card.....

Yep, this is supposed to be a unique, world-wide number, but some OSs let you alias that number.... I know that Kubuntu and FreeBSD allow this because I currently alias the MAC address on all my systems, to evade analysis and for plausible deniability in case of investigation.    Kind of cool, if you think about it.

[freewoman]

I have no say in the matter.  This computer was someone else's; when part of my job changed, I had to trade my upgraded Dell for her old Compaq preloaded with Windows ME.  Our corporate offices only service the Dell products that we purchase through them; long story.  I'm not very computer-savvy, though I'm learning; since my divorce I've had to figure things out for myself!  My boss has to clear me to call the local computer repair people, and she's been too busy.  Would prefer to work for myself but that's not happening at this point.  So I gotta do what I gotta do.  Thanks again for all the suggestions; I should have time today to print them off and give them a try.

[freewoman]

I did try some of the suggestions provided, but I didn't have time to go through the whole sequence of numbers (2 to 254!) that were recommended.  However, on Friday morning, the corporate offices were doing some sort of maintenance.  Evidently they fixed the issue, because I'm now able to get onto our DSL service.  So I guess it was a network problem after all.  Thanks for the suggestions, though.  Because my computer is no longer supported by the Help Desk (or Helpless Desk, as we refer to it), I wouldn't have been able to request assistance from our corporate offices.  Sometimes things turn out better than expected!

BTW, when I mentioned that "I would have to hire someone", the company would pay for it, not me.  I just have to make the calls and arrange for the repairperson to show up.  Which is sometimes easier said than done!