You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Anyone knows the TCP/IP Port that AppleShare use?
- Thread starter ddma
- Start date
We don't like Ads much either, but they do help cover the costs of running the site. Please consider turning off your ad blocker. Thank you.
I guess it is A) TCP. If you use Brickhouse to configure your firewall you have to allow tcp on port 548. Then connections to your X-Machine can be established.
I found out that udp has something to do with the ablility to see network machines in the "connect to server"-dialog. If you don't allow udp on several or all ports machines will not apeare in the dialog. Plus those ports are in the low 5000 region and constantly changing.
I found out that udp has something to do with the ablility to see network machines in the "connect to server"-dialog. If you don't allow udp on several or all ports machines will not apeare in the dialog. Plus those ports are in the low 5000 region and constantly changing.
UDP and TCP are different in that UDP is a 'fire and forget' protocol, useful for broadcast functionality (such as a computer broadcasting on a network that it is alive). Connections between computers do not need to be set up.
TCP on the other hand manages the delivery of the packets and sets up a connection. If the TCP application is well written then it will detect when the connection has died and will attempt to re-establish it. Because TCP manages the delivery of the packet more than UDP then it is a more intensive protocol. This is one of the reasons why (for example) a 56k modem connection doesn't deliver the full 56k of data bandwidth. It may be delivering something near that, but quite a lot of bandwidth is taken up with the TCP wrapper around the data packets and packets being re-sent, etc. UDP is a much lighter weight protocol that can be used when speed is more of an issue than guarunteed delivery.
At the end of the day most applications don't really care that much which IP wrapper is used to send the data packets. I used to have a lot of fun changing the default in Win NT to various formats. The default is UDP, but this is not allowed through many firewalls, so I changed a couple of my servers to be tunnelling HTTP protocol which got around the problem (as long as the client machine was set up similarly).
TCP on the other hand manages the delivery of the packets and sets up a connection. If the TCP application is well written then it will detect when the connection has died and will attempt to re-establish it. Because TCP manages the delivery of the packet more than UDP then it is a more intensive protocol. This is one of the reasons why (for example) a 56k modem connection doesn't deliver the full 56k of data bandwidth. It may be delivering something near that, but quite a lot of bandwidth is taken up with the TCP wrapper around the data packets and packets being re-sent, etc. UDP is a much lighter weight protocol that can be used when speed is more of an issue than guarunteed delivery.
At the end of the day most applications don't really care that much which IP wrapper is used to send the data packets. I used to have a lot of fun changing the default in Win NT to various formats. The default is UDP, but this is not allowed through many firewalls, so I changed a couple of my servers to be tunnelling HTTP protocol which got around the problem (as long as the client machine was set up similarly).