LabVIEW deployment problems

[kenavt]

When I attempted to deploy the code via an ethernet cord with the wi-fi adapter turned off via the hardware switch on my laptop, the deployment was faster, but not the speed it should be still.

Normally, my team has our radios put away and we don't use them at our shop, but I pulled one out and hooked it up. Deploying over the bridge WAS at normal deploying speed (a big relief). Success.

I believe the issue is with my computer's hardware (perhaps the motherboard, I don't know much about computer hardware). I have had problems with my USB ports in recent days, after I spilled a little pop on my laptop. I thought the only consequence was one sticky key, but it appears that it has infiltrated my laptop's case and gotten on the hardware. That probably explains my USB ports (which are physically located next to the sticky key, CTRL) and my ethernet port (which is a little farther away, but on the same side).

Either way, thanks a lot, Mark and Alan. I see the hard work you guys do helping others to fix their programming issues, and I can tell you that it means a lot to me, personally, as well as the others, I am sure. I don't think I can say thank you enough! Thanks!

[FourPenguins]

My team had a similar issue until the NI rep at Buckeye told us to disable Windows firewall. I don't know if that's the issue here (especially given the suspect hardware in your laptop), but he said that that was often the cause of connection/deployment problems.

[torihoelscher]

Originally Posted by FourPenguins

My team had a similar issue until the NI rep at Buckeye told us to disable Windows firewall. I don't know if that's the issue here (especially given the suspect hardware in your laptop), but he said that that was often the cause of connection/deployment problems.

That is true!!!
What my software mentor tells me and I sometimes remind him:
1) turn off wireless
2) turn off firewall
3) ping using cmd
4) if you cant ping power cycle
5) check ip address on computer
5.5) Use Measurement Automation Explorer
6) Reimage CRIO