[WT-support] Fwd: UDP socket #10013 Error

[Bob Wilson, N6TV]

OE1MHL reported a similar problem last April.  His last message indicated
the following:

2. On the ACER Travelmate, I uninstalled WinTest and also the Modem Software
> MOBILE CONNECT.
> 3. With the Registry Mechanic I made a deep Scan on that machine, for being
> sure that there is nothing left from the programs.
> 4. Then I installed WinTest, made the Configuration and so on, and also
> setup the loop back. WONDROUS its running!!!
>

So if you are using a mobile Internet connection of any kind make sure you
have the latest and greatest driver.

Otherwise, please send me screen shots of all of your key configuration
windows in Win-Test and WtDxTelnet, and the output of DOS commands IPCONFIG
/ALL and ROUTRE PRINT as well.

To capture a screen shot in Win-Test or any other program:

   1. Open the window (e.g.type SETUP [Enter]) and make sure it is "active"
   and has the focus.
   2. Press Ctrl-Alt-Shfit-PrintScreen (maybe AltGr-Shift-PrintScreen on a
   Eu. keyboard?). This copies the active window the clipboard
   3. Start, Programs, Accessories, Paint
   4. Edit, Paste
   5. File, Save as, File Type:  screenname.png (Portable Network Graphics)

73,
Bob, N6TV

On Wed, Jul 9, 2008 at 4:01 AM, Dieter Kritzer <oe8kdk at oevsv.at> wrote:

>
> Hello!
>
> Since a few months if have a problem to use Win-Test with the Cluster on my
> Computer.
>
> Win-Test alone workes fine, also WtDxTelnet.
>
> But when i have both programms with the same Broadcast-IP Address i have
> the
> Error:
>
> "Error opening UDP socket #10013"
>
> In Win-Test sometimes a Error is showen up: "Ethernet: error sending UDP
> protocol #10038"
>
> I tryed many different Port-Numbers, also turning off Fire-Walls, but no
> communication between WtDxTelnet and Win-Test.
>
> The same Problem is now, when i try to use the Tunnel for the HQ-Contest.
>
> This problem is the same on 3 different computers, also a friend of mine
> has
> the same problem on one computer.
>
> Any idea?
>
> 73 Dieter OE8KDK
>
>
> -------------------------------------------------------
> I wrote a mail to Larry yesterday, here his infos:
>
> Usually, a firewall and/or some "protection software" (!!!) incompatibility
> (or setting). The thing is that these f*cking things are usually hidden and
> very had to find. I know some guys who even had to totally reinstall
> Windows
> to disable them !
>
> Sometimes you can find what process is blocking the port access with the
> netstat utility (in a command line wnd) like
>
> netstat -a -b -p UDP
>
> Maybe you can try.
>
> Also, check you installed and run all WT apps with the local Admin rights.
>
> But, TBH, the "security softwares" (embedded in Windows or third-party) are
> the most probable cause.
>
>
> _______________________________________________
> Support mailing list
> Support at win-test.com
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.f5mzn.org/pipermail/support/attachments/20080709/c9eddd58/attachment.htm