I've got web services that work fine on my development machine, and on a
machine on our network.
I need to put them in our DMZ. Oh yea, I have to say, I don't have remote
access to these machines, so I have to deploye with a floppy disk and copy
the files over. I'm using framework 1.1 and VS.net v2 to build the web
service.
My first problem is this, on the w2k box, in our DMZ:
1. When I invoke function 'A' from the asmx file on 127.0.0.1 (the box in
the dmz), it works fine.
2. I go to the SAME asmx file over the internet & invoke function 'A', and
IE just spins & spins. No error is returned, and I know the function is
being called because it writes a text file to the web server & I see it
being written. But IE is still running and I have to just eventually close
the browser.
3. A second function 'B' which wraps a legacy com object, fails after
trying to instantiate that com object.
Next I replaced the w2k box in the DMZ with a w2003 box (same web service,
same IP address):
1. Function 'A' works fine. IE stops spinning after about 2 seconds.
2. However the function 'B' which tries to instantiate that com object,
still fails.
Now for the really confusing thing: On our w2k server in our network, both
functions work fine!! Same code, same etc/hosts file, albeit a different IP
address and its not in our DMZ. However I am unsure whether this is a DMZ
issue at all.
Also on all 3 boxes I deployed the same way: I went into IIS, created a
subweb (a website under the default one), hit the 'create' button to make it
an 'application'. Then I copied in the ws folder from my development
machine containing the asmx, the bin, .cs pages -- everything except the
vti_ folders :) . Also remember I'm seeing the ASMX page fine on all 3
boxes: the w2k & w2003 in the DMZ, and the w2k on our network. But I'm at
a loss as to why the ones in the DMZ are experiencing problems. I'm
wondering if there's something I did a couple years ago when I first
deployed on our network server, that I'm forgetting now? I made sure the
etc/hosts files are the same. I also made sure the web.config in each has:
<webServices><protocols>
<add name=HttpGet"/> and <add name="HttpPost/>
</protocols></webServices>
Thanks for any help & sorry for the rambling :) -- Jason Shohet