System restore has stopped working after an IP conflict

[Guest]

I plugged an ethernet cable between my PC and a router and I immediately got
an IP address conflict. This seems to have had some knock on effects to the
OS.

The IP address conflict seems to be between my ethernet adaptor and my
wireless PCI adaptor.

Since this happened:
- My desktop is all screwed up - e.g. some file icons are on top of each
other , and there is a garbled Microsoft Office Assitance - Onenote section
across the top of the screen
- System Restore won't work and recover to an old position.

Would appreciate some advice on what the next step should be or am I looking
at a rebuild?

thanks

 

[Guest]

Update - I've managed to tidy up the Desktop now, but System Restore is still
not working

 

[Guest]

Network Diagnostics shows the IP address of the Wireless PCI Adaptor being
192.168.0.2. The Ethernet Adaptor has no ip address however (I guess this is
because it is unplugged?)

 

[Guest]

I've managed to get system restore to work by running it in Safe Mode.

I've not managed to sort out the ip config, I'm leaving that unplugged for
the time being as I don't know how to sort it. (Advice appreciated on that
aspect)

Any other advice on what I should do here? I'm concerned I may have damaged
the OS or am I worrying too much?

 

[Patrick Keenan]

I've managed to get system restore to work by running it in Safe Mode.


I've not managed to sort out the ip config, I'm leaving that unplugged for
the time being as I don't know how to sort it. (Advice appreciated on that
aspect)

Go to start, run, type cmd. At the command prompt type ipconfig. This
will display the results of the adapter assignments.
This pair of commands at the command prompt will release and renew the IP
address for the adapters, and either resolve conflicts or show you why they
are appearing:

ipconfig /release <press enter>

(You should get back a report saying that the addresses are now all 0.0.0.0)

ipconfig /renew <press enter>

(this will get new addresses from the DHCP server as long as the adapters
are set to DHCP, the default)

If you get a message that an adapter is not in a state to have this
operation performed, it's likely that you have it set to a fixed IP address;
change this or ajust the router's DHCP range to exclude the fixed addresses.
If you get a message stating that it's disconnected, connect the cable and
try again.

Open Control Panel, open Network Connections, and examine the TCP/IP
properties of each. Usually, you will have them are set to automatic, not
fixed. You would usually want a network device set to fixed when it needs
to be at a specific, known location. Network printers are a good example of
things that need this stability. Set the router's DHCP range to not
include the section you will use for fixed addresses - otherwise, conflicts
are likely to occur.

If for some reason you cannot exclude a range, set the fixed addresses to
the upper limit and work backwards (so the fixed addresses would start at,
say, 192.168.0.253 and the next would be 192.168.0.252). This will help
but will really only delay conflicts.

Any other advice on what I should do here? I'm concerned I may have
damaged
the OS or am I worrying too much?

It isn't a sign of OS damage, but rather of misconfiguration. It's usually
something simple.

HTH
-pk