We help IT Professionals succeed at work.

UDP Packets Through MS Proxy Server...

awd
awd asked
on
Medium Priority
589 Views
Last Modified: 2013-12-23
What steps are necessary to enable a PC connected to the internet through MS Proxy Server on a Dial-Up connection (Win 95) to process TCP and UDP packets on ports 6112 and 6113? I can currently only process TCP packets. I need detailed information. I hope the points offered are sufficient. If not let me know.
Comment
Watch Question

Commented:
In Internet Service Manager, double-click the computer name next to the WinSock Proxy service, click the Protocols tab, and then click Add.

In the Protocol Definition dialog box, in Protocol name, type a name for this protocol definition.
 
Under Initial connection, in Port, type a valid port number on the server that will be used for the initial connection.

Under Type, click either TCP or UDP.

Under Direction, click either Inbound or Outbound.

Click OK and verify that the new protocol definition appears under Protocol definitions.

Click Apply, and then click OK.

You can use the following procedure to complete the Port Range Definition dialog box, which describes how to set port ranges for subsequent connections. Subsequent connections are those that originate as a result of requests or packets sent on the initial connection's port number. The subsequent connection parameters include the port number or range, the protocol type, and the direction. You can add, edit, or remove port ranges for subsequent connections. In addition, there can be one or more configurations for subsequent connections.

Note    A port range setting of 0 for inbound connections indicates Port_Any, which allows the server to select the port from the range 1024–5000.

To complete a port range definition for subsequent connections
In the Protocol Definitions dialog box, under Port ranges for subsequent connections, click Add.
In the Port Range Definition dialog box, in Port or Range, type a valid port number or a range of port numbers.
Under Type, click either TCP or UDP.
Under Direction, click either Inbound or Outbound.
Click OK, and then click OK again.

After you do this, you need to add group(s) to the access list so users can connect with your newly defined protocol.
awd

Author

Commented:
Thanks for the reply! If I understand correctly all of these comments and changes pertain to the SERVER. Is that correct? Is there anything that needs done on the CLIENT computer?
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION
awd

Author

Commented:
How do you install the WinSock Proxy client? Where is the mspclnt share you mention located? I appreciate your "patience" and the level of detail you are providing.

Commented:
When you install MS Proxy, by default the mspclnt share is created on the proxy server (look in network neighborhood).  The actual path is \proxy\clients on the drive where you install Proxy.
awd

Author

Commented:
I have not forgot about you. My ISP is dragging their feet on this. I should be able to confirm the answer by the end of this week. Sorry for the delay. Thanks for the help. I'll let you know as soon as I find out anything.
awd

Author

Commented:
This is probably a simple question, but we (me and my ISP) are having trouble with this. Given that I have a dial-up connection, what steps are necessary to map a drive (steps for server and client)? Say for example that the server machine name is "ISPServer".
awd

Author

Commented:
I have one more question related to this. Given that I need to install from the mspclnt share, how do I access that share to be able to preform the install? I guess I would need to map a drive to access the share. What steps have to be performed on the client and the server to make this possible? If it matters this is through my ISP over a dial-up connection.

Thanks for the help!
awd

Author

Commented:
Also, you mentioned that there are better ways for larger sites. Can you elaborate on this? I am willing to raise the point value of the question if you feel that 200 is not a fair valuation, especially with the additional questions.

Thanks again.

Commented:
For the large site question pertaining to WinSock client install: You could write a logon script.  The is also a provision for installing the client via URL.  See the online docs.

For mapping a drive:  from the Explorer Tools menu, select map drive.  Enter the UNC path to the share, in this example "\\ISPServer\mspclnt".   Is the Proxy on the other side of the dial-in?  If so, I would use the URL method for client installation.


awd

Author

Commented:
Yes. The proxy server is on the other side of the dial-in.

Commented:
For the large site question pertaining to WinSock client install: You could write a logon script.  The is also a provision for installing the client via URL.  See the online docs.

For mapping a drive:  from the Explorer Tools menu, select map drive.  Enter the UNC path to the share, in this example "\\ISPServer\mspclnt".   Is the Proxy on the other side of the dial-in?  If so, I would use the URL method for client installation.


Commented:
might bebetter to have your ISP send the contents of the mspclnt folder to you.  You can then create a share on one of you boxes and install from there.
awd

Author

Commented:
That is an interesting workaround! Would this actually work? If so it would solve the problem. They have already set up everything for me to ftp the contents of that folder to me. Doing it this way won't create any conflicts? Different machine names on the share and everything. Or have you done this before and confirmed that it works?

Commented:
No, I have put the proxy on the box doing the dial-in  No proxy here, so I can't look at the contents of the mspclnt folder and it's been some time since setting this up.  I remember connecting to the share on the proxy server and I think I ran an executable.  Machine names shouldn't matter, just whether the installation exe gets stuff outside the mspclnt folder.  I don't think it does, but haven't confirmed.
awd

Author

Commented:
I increased the points for you.

I got the client installed. Now with it running I am unable to even connect to the computer on port 6112 TCP. Before the problem was only with UDP packets. Is there any ways to troubleshoot where the problem lies (client/server) or ideas on what the problem would be? If I turn off the proxy client I am back to the UDP problem.

Thanks.

Commented:
Are your clients logging onto the same domain as the Proxy Server?  I ask because permissions are run by NT Domain User Groups/Accounts
awd

Author

Commented:
How could this be checked? With the client software (winsock proxy client) disabled I can connect to the computer over 6112 TCP. This still goes through the proxy server. Does it work differently with the client software enable, with respect to the domain? It should be the same user account, shouldn't it?
awd

Author

Commented:
The ISP says yes. I (the client) am logging into the same domain as the proxy server. I just spoke with them and they confirmed this.

Commented:
ok.  if the domain is same, and the protocol/port combination is defined in the WinSock properties on the Proxy, then the other thing is the access list.....what groups have permission to use the protocol/port combination.
awd

Author

Commented:
I'll have to check on that. How do the "mspclnt.ini" file and "wspcfg.ini" files relate to each other. The settings I was changing in the "mspclnt.ini" were getting reset periodically.
awd

Author

Commented:
I think this question has been going on long enough. Thanks for all of the help. Here are your points.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.