home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.sybase
- Path: sparky!uunet!wupost!gumby!destroyer!cs.ubc.ca!news.UVic.CA!haida!justice
- From: justice@dao.nrc.ca (Gerald Justice,P=363-0055,R=152A)
- Subject: Re: Can SYBASE Server listen on two ethernet interfaces?
- Message-ID: <1993Jan8.020704.5829@sol.UVic.CA>
- Keywords: SYBASE server ethernet interfaces subnets
- Sender: news@sol.UVic.CA
- Nntp-Posting-Host: haida.dao.nrc.ca
- Reply-To: justice@dao.nrc.ca
- Organization: DAO/CADC .
- Date: Fri, 8 Jan 93 02:07:04 GMT
- Lines: 36
-
- Not so long ago I asked about this and one person did reply with a suggestion
- to change the interfaces file master entry to refer to nullhost rather than
- the server's own real name. However, Sybase Tech Support finally found their
- own documentation on this after some weeks and the real answer is that you
- can have as many master entries in the interfaces file for the protocol/port
- combinations that you have. In our case we simply added a new line for the
- alternate hostname assigned to the second ethernet port, e.g.
- The interfaces entry was:
- SYBASE
- query tcp sun-ether primename 2025
- master tcp sun-ether primename 2025
- console tcp sun-ether primename 2026
- debug tcp sun-ether primename 2027
-
- And it now is
- SYBASE
- query tcp sun-ether primename 2025
- query tcp sun-ether secondname 2025
- master tcp sun-ether primename 2025
- master tcp sun-ether secondname 2025
- console tcp sun-ether primename 2026
- debug tcp sun-ether primename 2027
-
- The key on the server end is the master line not the query line.
-
- Tech Support has a short note (with no apparent title or name) about this and you
- might have trouble convincing them of this.
-
- ---
-
- Phone: (604) 363-0055 PDT Fax: (604) 363-0045 Telex: 049-7295
- Internet: justice@dao.nrc.ca Mail: Dominion Astrophysical Observatory
- National Research Council (Canada)
- BITNET: justice@nrcdao 5071 W. Saanich Road
- Victoria, B.C. CANADA V8X 4M6
-
-