Most wireless routers (such as Apple’s Airport Base Station) use DHCP/NAT to support wireless connections. Using the example found above: if you set your Client computer’s TCP/IP configuration with as a search domain, you can connect to our tech support database by entering just techdb in Helix’s Find Server field.Īssign multiple IP addresses to a Helix Server and Clients will be able to connect to it through any of the addresses.Īssign a different IP address to each interface and Helix will be able to communicate through all of them. If your Helix Server is on a computer with an assigned machine name (an A or CNAME record), you can enter the domain name in your TCP/IP configuration’s “search domains” field. On your local network, just enter the Bonjour name of your Helix Server to establish a connection. Helix 6.0 and later support Bonjour network identities. Now you can assign meaningful names (e.g: ) to your Servers. In the Helix 5.0-5.2.1 implementation the Client was required to enter the dotted IP address (example: 209.50.129.50) to locate a Server. If your Helix Server is on a computer with an assigned machine name (an A or CNAME record), you can simply enter the machine name to locate, whether connecting locally or remotely. This enhancement (as compared to the Helix 5.0-5.2.1 implementation) means that you can use DHCP/NAT servers to distribute a single public IP address to all of your office’s computers, while also giving external Clients access to the database. Setting up Helix’s TCP/IP implementation is very simple, and the few areas which may require network administrator intervention are mentioned below.Ĭlients on an intranet using private addressing can locate a local Helix Server either by entering the Server’s IP address or its Bonjour (aka Rendezvous or Zero Config) name. DHCP, NAT, and Firewalls are now fully supported in both directions. See the Client Connections in Helix 7.0 page for updated connection information, and come back here if you need additional technical information.īeginning with version 5.3, Helix includes a robust implementation of TCP/IP that supports virtually all currently common network environments.
Helix 7 (and later) users can almost certainly dispense with reading this technote, as connecting is now completely transparent. If you are using 5.0 through 5.2.1 this link takes you to the correct page. This note discusses the TCP/IP implementation in Helix 5.3 and later. Overview Services techdb Helix 8 Technotes Helix 7 Technotes Tips Issues Scripts Chat Repair Feature Requests Bug Reports FTP FAQs
#HELIX SERVER FIU PROFESSIONAL#
Technical Educational Professional 3rd Party Contact Us
0 kommentar(er)
