ASP.NET 2.0 web host suggestion (that does NOT block port 6103) RE: [libRETS-users] Getting "curl error #7 (couldn't connecttoserver)" error from live web server (but not localhost)

[Tech at ZolMedia.com]

It's a shared Windows host, and I found outlast night that they do indeed
block all non-standard ports.

Also, after I'd sent the message to this group, I did a simple (doh!) test,
where I ran the web app on my localhost, but disconnected the Internet.
Guess what? "CURL ERROR #7"
 
I'm looking into other hosts now. Anybody have suggestions for an
affordable, but ASP.NET 2.0-centric web host with good tech support? 

-----Original Message-----
From: librets-users-bounces at crt.realtors.org
[mailto:librets-users-bounces at crt.realtors.org] On Behalf Of Dave Dribin
Sent: Thursday, January 04, 2007 9:46 AM
To: For discussion and help for and by the users of the libRETS C++ library
Subject: Re: [libRETS-users] Getting "curl error #7 (couldn't
connecttoserver)" error from live web server (but not localhost)

On Jan 3, 2007, at 11:34 PM, <Tech at ZolMedia.com> wrote:
> I know that the server name and port are correct because they work 
> when run from http://localhost. They just don't work when run from the 
> live server.

Sounds like a firewall issue, to me.

> Not sure what Wireshark is, but I assume you have to install and run 
> it on the web server with the problem, right?  I can't do that on the 
> live web server because it's a remote shared host.

Yes, it's something you would run on the same machine that the librets code
is running on.

> Would I also get this error if the shared host was blocking outgoing 
> connections?

It's a possibility.  It all depends on how the intermediate firewalls are
setup.  Is this shared host Windows or Unix-based?

-Dave

_______________________________________________
libRETS-users mailing list
libRETS-users at crt.realtors.org
http://mail.crt.realtors.org/mailman/listinfo/librets-users