I have a fully working CS system. There are 9 staff with laptops. Its a B-Y-O-D situation, so it is a mess of different laptops.

1 device will not connect to the EDB Server on the network LAN.

I get an EDB Error #1100 "An attempt was made to access a socket in a way forbidden by its access permissions. (10013), on API 'connect'".

I can PING the server no problem. File transfer / sharing is all A-OK too.

I have switched off Windows Defender, the firewall and anti-virus software at the suggestion of other websites, without success.

I can see references which say I need to "disable VNC Server" (although it is not clear whether this applies to Windows 8) but I can't find this service detailed anywhere, so I'm guessing this isn't the problem.

Googling it suggests it has something to do with network-rights and settings, I am guessing that in Windows 8 M$ have "improved" the way these work in some wonderfully new and complicated way ...

Does anyone have any ideas, I am not particularly good at network-stuff, especially on Windows 8

The problem is definitely not with EDB, it is with the Win 8 set-up, I just don't know what more I can do.

Adam


Wild guesses

1) could it be the network type that the W8 notebook is set at? Public / Private / Work - have a look in Control Panel | Network & Sharing Center

2) is network discovery turned off

3) possibly sleep - I have an annoyance with a Gateway notebook - when it goes to sleep its still visible on the network but I can't access it


Roy Lambert

On 10/4/2013 5:31 AM, Adam Brett wrote:
> 1 device will not connect to the EDB Server on the network LAN.
> I get an EDB Error #1100 "An attempt was made to access a socket in a way forbidden by its access permissions. (10013), on API 'connect'".

This usually indicates that your app cannot bind to the port. Usually
it's caused by something else already listening on the port or something
preventing app to bind to the port (security like AV software, etc).

I usually use utility called TCPView (from Microsoft Sysinternals) to
see what's listening and on what ports :

http://technet.microsoft.com/en-us/sysinternals/bb897437

I assume your problem refers to your app which acts as client side of
the C/S connection so it would dynamically pick a local port when
connecting.

Hence i'm more likely leaning towards something blocking it from
binding. I know you said you turned it off bu i would double-check - not
sure what you turned off but for some of them (Kaspersky i know
personally) you need to specifically disable the TCP protection - just
turning off real-time AV is not adequate. McAfee/Symantec i believe were
same way also

Raul

Wow, thanks both for these brilliant & thorough replies ... Network problems a really not my area

Sure something in these suggestions will do the trick.