To be more precise...since your client can access the server outside the client firewall, you already know the server port. Just check to make sure your client firewall allows "outgoing" HTTP. I'm guessing it doesn't.
You don't need to enable "incoming" for a particular port on your client unless you want to allow outsiders to send requests to that port on your client box, like if you want to receive asynchronous notifications. For the most part though, your client is probably only sending "outgoing" requests, and responses will be received on that same synchronous connection. -----Original Message----- From: Vinh Nguyen (vinguye2) Sent: Friday, June 13, 2008 1:02 PM To: [email protected] Subject: RE: client port I guess the question is: is this firewall on the client side, or the server side? After reading the original email again, looks like it's on the client side. My answer still applies though. You need to check what port is used on the server side for HTTP. Then, make sure that same port is opened by the firewall on your client side. -----Original Message----- From: danclemson [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2008 12:51 PM To: [email protected] Subject: RE: client port Hi, The client can connect to the service if it's outside its firewall. The problem is when it is behind its firewall. So, I do not think there is issue with firewall/port of the service side. Vinh Nguyen (vinguye2) wrote: > > Hi, > Normally, a server would have port 80 or 8080 as the default for HTTP > connections. So first, you need to check if your server/firewall > allows incoming HTTP at all. If it doesn't, then your web service > can't be accessed. > > But if it does, then you need to check what port number is assigned > for HTTP. Your client would then send requests to the server using > that port. > > Note that some firewalls have separate configurations for outgoing and > incoming, so you have to check both, too. > -Vinh > > > -----Original Message----- > From: danclemson [mailto:[EMAIL PROTECTED] > Sent: Friday, June 13, 2008 11:08 AM > To: [email protected] > Subject: client port > > > Hi, > > I am new to web services and axis2. > i host a web service, and my client is behind a firewall(no proxy). > > The client can connect with my service if it's outside it firewall, > but could not communicate with service if behind its firewall. what > might be the problem? > > When the client send request to server, which port is used or is there > any default port? If the firewall lets the request out, will it blocks > the response send in by the service server as the port is not opened > at firewall? > > thanks for help. > -- > View this message in context: > http://www.nabble.com/client-port-tp17829239p17829239.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/client-port-tp17829239p17830818.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
