Why this is happening can depend on things from what version you are using, what IDE you are using, what properties you have set, etc. The quickest way to solve this issue is to do a web.config redirect and to copy your images local to your application. Here is a KB article to achieve this:
http://devcenter.infragistics.com/Support/KnowledgeBaseArticle.aspx?ArticleID=6158
If you tell me your NetAdvantage version and CLR, Visual Studio version, and the aspx markup of one of your problem controls, it will help in determining the cause of your issue.
Were you using CLR 1.x controls before? If so, certain image properties would have an image specified and would keep it from using the embedded resources.
Sung Kim"]Were you using CLR 1.x controls before? If so, certain image properties would have an image specified and would keep it from using the embedded resources.
Were you using presets before?
The directory in your rendered page is pointing towards this directory C:\Windows\Microsoft.NET\Framework\v2.0.50727.
I believe it is trying to find the files that we used to copy there when installing before removing the support of presets. You can either copy those filies manually to this location, consider using Application Styling, or just doing what you are doing now.
If you check in your laptop where it is working, I bet you will find these images in the folder I mentioned above.
It is because the JavaScript is stored in the dlls as embedded resources. We also do this for certain images but did not want to bloat the dlls with images that may or may not be used (such as those in presets).