Registered: Jan 2002
Location: Saskatoon, Saskatchewan
Posts: 1055

Okay, here goes.

I've run into a Windows 2003 server (With SP1) that's blocking information from getting to a service. The service runs on port 8080. There is no conflict. It starts without a problem and throws no errors. I've port scanned the server. The port is open. The windows firewall service is completely shutdown. I can get it to run on all of my other machines, including another Windows 2003 Server. I can fire up IIS and create a website on 8080 and access it no problem.

There's nothing in the Event view that tells me anything.

What could be interfering? I don't even know what more information to give...

Anybody?



Can't access it on 127.0.0.1:8080
Can't access it on localhost:8080
Can't access it on it's assigned ip at 8080

Last edited by Super Gremlin on 01-11-2006 at 11:12 PM

Report this post to a moderator | IP: Logged

Registered: Nov 2000
Location: UK
Posts: 4736

Any clue as to what the service actually is? If I was to guess you're either missing a dependency(some of the .NET debugging stuff doesn't make it explicitly clear all the services that it needs running and will fail in random ways if they're not around) or the application has some built in access controls.

Report this post to a moderator | IP: Logged

Registered: Jan 2002
Location: Saskatoon, Saskatchewan
Posts: 1055

The service is an application add on designed by my company. It runs for every other client everywhere else in the world, but this one particular clients can't get it running on any of their production servers. They tested again tonight on a Windows 2000 server and still were not able to get it up and running.

Their staging server on the other hand ran it without a problem... Isn't the point of the staging server that it's supposed to be an exact clone of the production server?

Report this post to a moderator | IP: Logged

Registered: Aug 2000
Location:
Posts: 1725

Let me see if I have this right.... The guys that designed the product, can not figure out why their own design will run on one box, but not another?

Report this post to a moderator | IP: Logged

Registered: Aug 2001
Location: Hilbert Space
Posts: 35561

That's not that weird, surely? You'd have to know all of the client's setup, at least. Presumably they will eventually work it out.

Report this post to a moderator | IP: Logged

Registered: Apr 2005
Location: summer!
Posts: 10456

maybe another service is already using the port.

Report this post to a moderator | IP: Logged

Registered: Jan 2002
Location: Saskatoon, Saskatchewan
Posts: 1055

quote:

---

Originally posted by amerikanjunkie
Let me see if I have this right.... The guys that designed the product, can not figure out why their own design will run on one box, but not another?

---

Report this post to a moderator | IP: Logged

Registered: Jan 2002
Location: Saskatoon, Saskatchewan
Posts: 1055

quote:

---

Originally posted by dogcow
maybe another service is already using the port.

---

Report this post to a moderator | IP: Logged

Registered: Nov 2000
Location: UK
Posts: 4736

The only other thing I can think that's creating the problem is that there's some 3rd party firewall running on the machine. It's possible it didn't block the IIS stuff as it might be a trusted application, which your service wouldn't be.

Report this post to a moderator | IP: Logged

Registered: Jan 2002
Location: Saskatoon, Saskatchewan
Posts: 1055

That's what I was thinking too, but they swear up and down that if it can reach the port, it should run.

Report this post to a moderator | IP: Logged

Registered: Jan 2002
Location: Saskatoon, Saskatchewan
Posts: 1055

Nevermind. Got it working. Ridiculous.

Report this post to a moderator | IP: Logged