This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I am developing a web application on my notebook, ThinkPad X60, which has both LAN and Wireless LAN. When I connect to a network. I can deploy my web application and use any feature well. When I unplug my LAN (usually I use LAN at my office), the ThinkVantage Access Connections will switch my machine to use Wireless LAN. In this case, I also can deploy my web application and browser start. When I turn off Wireless LAN (and no LAN), the ThinkVantage Access Connection show status "Disconnected". My web application cannot deploy and browser cannot start. The output is as follow: ... Starting server Bundled Tomcat (5.5.17) Starting of Tomcat failed, the server port 8084 is already in use. E:\JavaProjects\WebTest\nbproject\build-impl.xml:521: Deployment error: Starting of Tomcat failed, the server port 8084 is already in use. See the server log for details. BUILD FAILED (total time: 4 seconds) When I restart my machine and run NetBeans again with no network connection (both LAN and Wireless LAN), the output finish at the line "Starting server Bundled Tomcat (5.5.17)" and the annimation status of deploying web annimate for a long time. First times, I think that the problem is related to the ThnikVantage Access Connection. So, I tried to solve this problem by uninstall the ThinkVantage Access Connection, but the result is the same. After tried many ways. Then, I found that. When I work at home with no network connection, I can deploy web application if disable all network cards. (At the Network Connections window, right-click at each network (LAN and Wireless LAN) and select disable) I do not understand, why? Is this a bug? This happend on both NetBeans 5.0 and 5.5.
This does not seem to be a NetBeans issue, looks more like some local configuration issue. Try to ask on the nbusers mailing list, someone might have possibly encountered the same problem and already knows how to solve it.
Thank you, sherold. I found the solution. I found that the service "DNS Client" is disabled. After enable it, everything work.