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.

Bug 223119 - build hosts/network connectivity/-J-Djava.net.preferIPv4Stack=true/broken
Summary: build hosts/network connectivity/-J-Djava.net.preferIPv4Stack=true/broken
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Remote (show other bugs)
Version: 7.2.1
Hardware: PC Windows 7
: P1 normal (vote)
Assignee: issues@cnd
URL:
Keywords:
: 223413 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-12-02 00:47 UTC by willianma
Modified: 2012-12-06 20:57 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log (32.66 KB, text/plain)
2012-12-02 00:47 UTC, willianma
Details
A small test (1.12 KB, text/plain)
2012-12-02 14:32 UTC, Andrew Krasny
Details

Note You need to log in before you can comment on or make changes to this bug.
Description willianma 2012-12-02 00:47:23 UTC
Product Version = NetBeans IDE 7.2.1 (Build 201210100934)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.7.0_05
Runtime = Java HotSpot(TM) 64-Bit Server VM 23.1-b03


hi, 
the remote build hosts feature cannot see any computer on my network, even with all firewalls disabled.
i tryed to setup the option -J-Djava.net.preferIPv4Stack=true on the netbeans.conf file but it only enabled the access to the internet (which wasn't working previously)
the C/C++ Build Hosts/Add New Host button doesn't even open after set the -J-Djava.net.preferIPv4Stack=true
admin rights and disabling ipv6 protocol also didn't solve the issue.

it'd be wonderful if I could run my project in my linux machine and code it on my netbeans under my windows 7 laptop. I was hoping to get it working through ssh. as i'm trying to develop a server application for linux, netbeans shown being the best option. but couldn't get it to work on time.
Comment 1 willianma 2012-12-02 00:47:28 UTC
Created attachment 128701 [details]
IDE log
Comment 2 Andrew Krasny 2012-12-02 14:01:11 UTC
willianma,

please be sure to set correct proxy settings (I guess 'No Proxy' in your case).
This option is available either from Tools->Options->General or on the panel with 'Add Host' wizard... 
Also you could just type in the destination address/name and proceed without waiting for hosts being discovered... 

Could you try that? 

Thanks,
=Andrew
Comment 3 Andrew Krasny 2012-12-02 14:32:41 UTC
Created attachment 128716 [details]
A small test
Comment 4 Andrew Krasny 2012-12-02 14:34:03 UTC
willianma,

could you, please, run the small java code on your machine (attached).
Does it work?
Comment 5 Andrew Krasny 2012-12-02 14:41:06 UTC
willianma,

seems like you faced with this problem in JDK:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7112820

If you could provide additional information to that bug, please do ;)
Comment 6 Andrew Krasny 2012-12-02 14:55:03 UTC
http://hg.netbeans.org/cnd-main/rev/326c9b550c97

This is not a real fix, but a workaround that should allow user to proceed...
Comment 7 Quality Engineering 2012-12-03 03:01:22 UTC
Integrated into 'main-golden', will be available in build *201212030001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/326c9b550c97
User: Andrew Krasny <akrasny@netbeans.org>
Log: Bug #223119 - build hosts/network connectivity/-J-Djava.net.preferIPv4Stack=true/broken
Comment 8 willianma 2012-12-03 17:09:23 UTC
hi, thankfully I've solved the problem, that was an issue to ALL the Alienware Notebooks with the "bigfoot wireless card". this issue affects javaw.exe and netbeans. The fix is to reset the "netsh winsock reset" in the cmd as Admin and reboot the computer. The fix is instant but is needed to reboot in order to commit.
I was testing a server and client socket, and before my alienware only listened with the server and couldn't bind the clientsocket. the fix for that without resetting the winsock is here(not recommended)
//the clientSocket below is for connection problems on my alienware
clientSocket = new Socket("192.168.25.12" , 8889, inet.getLocalHost(), 0);
//clientSocket = new Socket("192.168.25.33",8888);
the args ("192.168.25.12" , 8889, inet.getLocalHost(), 0) sort the problem but is just a test. i'd recommend resetting the winsock. 

As a result I've discovered it, and there is nothing similar to this on the internet, i wish you could highlight my issue, so other alienware owners can know the workaround.
The winsock is mapped to the bigfoot wireless drivers so they can filter the traffic. but this is totally buggy and I highly recommend it to be remapped. 

regards,
Willian Mainieri
Comment 9 Andrew Krasny 2012-12-06 20:53:10 UTC
*** Bug 223413 has been marked as a duplicate of this bug. ***
Comment 10 Andrew Krasny 2012-12-06 20:57:16 UTC
Willian,

good to know that you have solved the problem!
And thank you for the information that could help others.

=Andrew