I have just fitted a touch screen console at work, it has a static IP address entered, but this is not what it needs to be, I have changed the IP address to what it needs to be but when the console is powered down the IP address reverts to what it was and causes an IP conflict on the network.
Im thinking the IP address is assigned in startup scrips or the like, is this correct and if so how do I find them to change it.

Cheers

BTW the OS is windows XP.

 

just out of interest, why are you using static IP's? and not letting your router or server deal with DHCP?

But as for the problem, is there mroe than 1 network adapter? i.e. built in wireless etc, if so are you 100% sure your changing it on the right adapter?

 

The network is on an oil rig, i guess its so that all IPs for different devices are the same from rig to rig as there are standard IP addresses assigned for each device no matter rig its on.

AFAIK there isnt a server or router, there are a number of SBC's which communicate with one another, then things like HMI's, remote I/O modules and VFD's on the ethernet network also.

Im certain im changing the ip address correctly, the hmi/touch screen is basically a computer with windows os on so im basically changing the ip address as i would on my laptop when im plugging into the network. Theres just something changing the IP address on boot up, the HMI is currently fitted and working but if i restart the IP will be reverted back to what it was and conflict.

Hope this makes sense,

 

Ahh i see, seems strange that something is changing the IP on start up though, is there some kind of network adapter BIOS? i.e. when the PC is booting does it say something like "press ctrl + N to enter network setup"? dont think that will be very likley but then i cant see why it would change a static IP address on start up..... may be worth ching it for viruses and malware etc... but again this seems unlickly as they are normally more malicious than just changing the IP address.....

 

Check the System event log to see if there are any errors during startup or shutdown - it may be rolling back to a previously known good configuration because the registry is for some reason corrupt.

Run chkdsk /f and restart it to make sure the disk is actually clean - filing system problems are often manifested by strange config errors . You could try to make the change, then disable System Restore and re-enable it, then restart the machine to see if the change remains in place. Disabling/re-enabling system restore will clear out any previous configurations that it may be reverting to.

 

Cheers guys ill give these a try

 

I wonder if this has a funny installation of windows like my digital signage systems at work.
If you make changes for example install some software then reboot it will wipe it and revert back to the last state that was booted up.
To make system changes stay you have to commit them by running a small script before you reboot.

If the other ideas dont work then try googling the model number of the console and see if something like this is embedded.

 

I think we have a winner!

Is the thing you have to run a batch file (.bat)? I was looking in the run menu earlier to try and see what had been run previously and what may have been changed at the factory. One of these files which didnt appear to do anything was C:\windows\writefilter_save.bat. After re-starting to check in the bios the IP address had stayed the same which had me somewhat baffled as I didnt know what id done to sort, but your post there has just made the penny drop!

Cheers for all your suggestions, id have still been waiting a couple of days for a reply off my tech support group!!!

 

nice one!

no worries, glad to help!