Load URL returns error 10049

Erin D. Smale esmale at welshpiper.com
Tue Nov 8 08:50:56 EST 2005


Hi Dave,

Based on the Winsock error, it may be that his local host file is 
defining an address that conflicts with the address in your app, or that 
resolves to an address that conflicts with his internal network 
(unlikely but possible).

As a test, have the user open IE and type in the URL directly. If he 
gets the same error, I would check his host file ot see what names are 
being resolved to what addresses. Also, you might want to have him open 
up a command prompt and use 'ping -a <your URL>' to see what address 
your URL it resolves to--if the host file is "interfering," the address 
may not resolve to the actual URL.

It would be helpful to know how he's getting his own IP, too (e.g., is 
it static or assigned via DHCP). Also try to determine what his default 
gateway is (especially if he's on an internal network behind a firewall).

As a temporary workaround, have him try to access the URL through the IP 
address; this skips DNS or host file name resolution and may offer a 
clue as to what's going on. Let us know what you find.

Cheers,

-- Erin

Check out The Chimera RPG:
http://www.welshpiper.com



Dave Beck wrote:

> 
>
>Hi,
>
> 
>
>I have a rev standalone that has been distributed to a number of users. The
>standalone uses the "load URL" command to get a web page from my server. The
>command works as expected for every user to which I've distributed the stack
>except for one. The load URL command fails for this user and the URLStatus
>function returns "error". Then the libURLErrorData function returns "10049".
>Does anybody have any idea what could be causing this error? The user is
>able to browse the internet with IE without problems before and after the
>error occurs, so I doubt it is a problem with her setup. The online info I
>could find on the error says it is related to opening invalid an IP address:
>
> 
>
>Winsock error 10049 typically occurs when you attempt to create a socket
>with an address not on this machine.  For example if you have MDaemon
>running on a machine with an IP address of 192.168.0.1 and you attempt to
>bind MDaemon to 192.168.0.100 you will receive this error message.
>
> 
>
>In truth that doesn't make a great deal of sense to me, but maybe there is
>somebody on this list that can shed a little light on the situation?
>
> 
>
>Thanks in advance.
>
> 
>
>Dave Beck
>
> 
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
>
>  
>

-- 

-- Check out The Chimera RPG: http://www.welshpiper.com



More information about the Use-livecode mailing list