Re: How can I make the server to call back to client without being blocked by firewall.
From: Bernie M (while_up_late@night)Date: 09/30/02
- Next message: David Schwartz: "Re: How can I make the server to call back to client without being blocked by firewall."
- Previous message: : "Help with ClosedBSD"
- In reply to: jeff Lee: "Re: How can I make the server to call back to client without being blocked by firewall."
- Next in thread: David Schwartz: "Re: How can I make the server to call back to client without being blocked by firewall."
- Reply: David Schwartz: "Re: How can I make the server to call back to client without being blocked by firewall."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Bernie M" <while_up_late@night> Date: Mon, 30 Sep 2002 19:47:00 +1000
I'm out of my depth when it comes to confirming whether tcp or udp is best
for this situation but have copied this thread to "comp.protocols.tcp-ip".
Those guys can throw in some ideas as to the pro's and con's of each.
I tend to think you would be on the right track suggesting a single TCP
session. As you said, the clients have to be logged in to make or receive
calls anyhow. It also reduces the complexity of additional ports being
allowed through firewalls etc.
Good luck.
BernieM
"jeff Lee" <jeff-lee@attbi.com> wrote in message
news:87Ol9.646820$UU1.113852@sccrnsc03...
> Thanks Bernie.
>
> You helped me cleared sth.
>
> Our application will have thousands of clients, and any one of them can
make
> connection to any one of others via our server. Therefore, our server has
> to somehow do a call back to tell the called client that somebody is
trying
> to
> reach him. I am sure we will hit fire wall when our server tries to open a
> connection
> to the client.
>
> We don't want to slack the client's fire wall at all, so I am thinking
> an always on TCP connections from the clients to our server may solve the
> problem.
> Anyway all the clients have to log in before they can make a call or be
> called.
>
> Do you think this will work?
>
> Also since UDP is connectionless protocol, it won't work for this, will
it?
>
> Thanks.
>
> Jeff
>
> "Bernie M" <while_up_late@night> wrote in message
> news:3d966c92$0$23173$afc38c87@news.optusnet.com.au...
> > "jeff Lee" <jeff-lee@attbi.com> wrote in message
> > news:7Vil9.38097$wH.4116@sccrnsc01...
> > > All,
> > >
> > >
> > > We are developing a client server applications, and speculating that
> > > the server may have the problems to make call backs
> > > because of the firewall.
> > >
> > > Can anybody tell me what technics / protocol to use to solve the
> problem?
> > >
> > > Regards,
> > >
> > > Jeff
> > >
> >
> > When you say "call backs" do you mean the server will initiate a TCP
> session
> > back to the client?
> >
> > To "solve the problem" you should be speaking to the firewall
> administrator.
> > As an application developer you should be able to provide the
> administrator
> > with specific information about what protocols, port numbers (perhaps
even
> > application specific url's etc.) that your application will need allowed
> > through the firewall.
> >
> > The last thing you want to do is to get off-side with those that can
help
> > you and, besides, you don't want to do anything that puts the companies
> > network at risk do you? Attempting to get around any restrictions may
be
> > (should be) a sackable offence.
> >
> > BernieM
> >
> >
>
>
- Next message: David Schwartz: "Re: How can I make the server to call back to client without being blocked by firewall."
- Previous message: : "Help with ClosedBSD"
- In reply to: jeff Lee: "Re: How can I make the server to call back to client without being blocked by firewall."
- Next in thread: David Schwartz: "Re: How can I make the server to call back to client without being blocked by firewall."
- Reply: David Schwartz: "Re: How can I make the server to call back to client without being blocked by firewall."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
