IP "mess" after new method test run

I added tags to this post to increase visibility.

A method should have no impact on the IP addresses of your PC or any of your instruments.If you needed to reformat/reimage your system in order to resolve the networking problem you ran into, then I suspect there is a larger problem afoot than just a corrupt method. This sounds more like an operating system or PC hardware problem.

I added tags to this post to increase visibility.

A method should have no impact on the IP addresses of your PC or any of your instruments.If you needed to reformat/reimage your system in order to resolve the networking problem you ran into, then I suspect there is a larger problem afoot than just a corrupt method. This sounds more like an operating system or PC hardware problem.

Is it possible for Agilent to load this method and see if it causes an error?

I whould realy like to see whats up with this..

thanks

If you are concerned that the method is corrupt, then the best thing to do is to create a new method from the default method. Getting secondary confirmation that the method is corrupt would not help you resolve this problem.