Port proxy and system for server and client computers

• US 20050010670A1
• Filed: 07/20/2004
• Published: 01/13/2005
• Est. Priority Date: 04/12/1999
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Softricity (Microsoft Corporation)
• Inventors: Schaefer, Stuart, Greschler, David M., Mysliwy, Owen
• Application Number:
  US10/894,671
• Publication Number:
  US 20050010670A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A method and system for serving software applications to remote clients across the internet, for example, is disclosed that preferably utilizes standard, SMB (server message block), protocols, which are available in commercial operating systems. Further, an associated business method is described in which subscribing institutions can out-source the application serving to a third party institution, transparently. Finally, a port proxy system is provided that enables tunneling through firewalls that are configured to block communications from SMB ports.

Claims

1. A method for enabling remote networking functionality by port proxying, the method comprising:

executing a process on requiring a networking protocol;

on a local client computer, intercepting communications from the process to a port assigned to support the network protocol; and

redirecting the communications over an open port on the client computer.

2. A method as described in claim 1, wherein the step of executing the process comprises executing an application program.

3. A method as described in claim 1, wherein the step of executing the process comprises executing an application program residing on a remote storage asset.

4. A method as described in claim 1, wherein the process utilizes SMB networking.

5. A method as described in claim 1, wherein the step of intercepting communications from the process comprises intercepting communications for port 139.

6. A method as described in claim 1, wherein the step of intercepting communications from the process comprises addressing the communications to an address assigned for local loop-back.

7. A method as described in claim 1, wherein the step of redirecting the communications over the open port comprises encapsulating the communications in an HTTP packet.

8. A method as described in claim 7, wherein the communications are located in a post data portion of the HTTP packet.

9. A method as described in claim 1, wherein the open port is an HTTP port.

10. A method as described in claim 1, wherein the open port is a FTP port.

18. A method as described in claim 1, further comprising constructing an application descriptor file for coordinating actions between a client and a server.

11. A system for remote networking by port proxy, the system comprising:

an application program executing on a client computer which is utilizing the SMB protocol to access a remote storage asset; and

a port proxy program, running on the client computer, that intercepts communications from the program to a port assigned to support the SMB protocol and redirects the communications over an open port on the client computer.

12. A system as described in claim 11, wherein the open port is an HTTP port.

13. A system as described in claim 11, wherein the open port is an FTP port.

14. A system as described in claim 11, wherein the SMB port is port 139.

15. A system as described in claim 11, wherein the communications are addressed for local loop-back.

16. A system as described in claim 11, wherein port proxy program encapsulates the communications in an HTTP packet.

17. A system as described in claim 16, wherein the communications are located in a post data portion of the HTTP packet.

19. A system as described in claim 11, further comprising an application descriptor file on a server for coordinating actions between a client and the server.

20. A system for enabling remote networking functionality by port proxying, comprising:

a client computer having a processor that executes software instructions;

a first client process, running on the client computer, that requires a networking protocol;

a second client process, running on the client computer, that intercepts communications from the first client process to a port assigned to support the network protocol and redirects the communications over an open port on the client computer.