开发学院数据库 Sybase 如何将不同网段或拨号环境下的客户端连接到ASA服务... 阅读

如何将不同网段或拨号环境下的客户端连接到ASA服务器

　2006-04-25 23:11:50　来源：WEB开发网　闂傚倸鍊搁崐椋庢濮橆兗缂氱憸宥堢亱闂佸湱铏庨崰鏍不椤栫偞鐓ラ柣鏇炲€圭€氾拷

闂傚倸鍊搁崐椋庣矆娓氣偓楠炲鏁撻悩鎻掔€梺姹囧灩閻忔艾鐣烽弻銉︾厵闁规鍠栭。濂告煕鎼达紕校闁靛洤瀚伴獮鎺楀箣濠靛啫浜鹃柣銏⑶圭壕濠氭煙閻愵剚鐏辨俊鎻掔墛缁绘盯宕卞Δ鍐冣剝绻涘畝濠佺敖缂佽鲸鎹囧畷鎺戭潩閹典焦鐎搁梻浣烘嚀閸ゆ牠骞忛敓锟�

婵犵數濮烽弫鍛婃叏椤撱垹绠柛鎰靛枛瀹告繃銇勯幘瀵哥畼闁硅娲熷缁樼瑹閳ь剙岣胯鐓ら柕鍫濇偪濞差亜惟闁宠桨鑳堕崝锕€顪冮妶鍡楃瑐闁煎啿鐖奸崺濠囧即閵忥紕鍘梺鎼炲劗閺呮稒绂掕缁辨帗娼忛埡浣锋闂佽桨鐒﹂幑鍥极閹剧粯鏅搁柨鐕傛嫹闂傚倸鍊搁崐椋庢濮橆兗缂氱憸宥堢亱闂佸湱铏庨崰鏍不椤栫偞鐓ラ柣鏇炲€圭€氾拷　　闂傚倸鍊搁崐鐑芥嚄閼哥數浠氱紓鍌欒兌缁垶銆冮崨鏉戠厺鐎广儱顦崡鎶芥煏韫囨洖校闁诲寒鍓熷铏圭磼濡搫顫岄梺璇茬箲濮樸劑鍩€椤掍礁鍤柛鎾跺枎椤繐煤椤忓嫬鐎銈嗘礀閹冲酣宕滄导瀛樷拺闂侇偆鍋涢懟顖涙櫠椤斿墽纾煎璺猴功缁夎櫣鈧鍠栭…閿嬩繆濮濆矈妲烽梺绋款儐閹瑰洤螞閸愩劉妲堟繛鍡楃箲濞堟﹢姊绘担椋庝覆缂傚秮鍋撴繛瀛樼矤閸撶喖宕洪埀顒併亜閹烘垵鈧綊寮抽鍕厱閻庯綆浜烽煬顒傗偓瑙勬磻閸楀啿顕ｉ崐鐕佹Ь闂佸搫妫寸粻鎾诲蓟閵娾晜鍋嗛柛灞剧☉椤忥拷

核心提示："Unable to start, server not found" - Client/Server on different subnets (network router used) or Dialup Connection SUMMARY:

"Unable to start, server not found" - Client/Server on different subnets (network router used) or Dialup Connection

SUMMARY:

Document ID:	TBA	Last Revised:	06/15/1998
Topic:		Document Type:	TechNote
Product:	Sybase SQL Anywhere	Version:	5.x
Platform:	PC	Operating System:	Windows NT / 95

Document:

　　Symptom:

　　User can ping the server, can map a drive to the server machine, can access files that are located at the server machine. However, cannot connect from client machine to the database server. This problem can cause the following error message: "Unable to start, server not found"

　　Cause:

　　The server and the client machines are in different subnets (There is a network router between the two machines) or the user is connecting to the server using a Dialup connection, such as ISP.

　　This is strictly a network design issue.

　　Solution:

　　If you are allowed to merge the subnets, follow Solution 1. Otherwise, follow Solution 2.

　　Solution 1 - For all network protocols

Put the server machine and the client in the same subnets (which means a change of network design).

　　Solution 2 - Specify server address, only for TCPIP and IPX

　　For TCPIP:

Obtain ip address of database server machine : server_ip_address
If the default port number for the SQL anywhere database server has been changed (default is 1498), obtain the port number being used : port_number
On the Client:

1) The database server name specified in the command line is case sensitive, make sure that the case used to specify the server name in client and server machines match.

i.e. On the server: Dbsrv50 –n –x tcpip SADEMO?.
On the client: Dbclient –x tcpip SADEMO

2) Specify host= parameter (This is specially requiered if connecting to a Netware Server).

3) If the default port number at the server has been changed, you will need to specify port= parameter

4) Specify the IP address of the Client, using the MYIP = parameter (ClientIPAddress)

dbclient –x tcpip{Host=server_ip_address;port=port_number, MYIP = ClientIPAddress} db_server_name

On the server, the start command line should be :

dbsrv50 –n db_server_name –x tcpip

Additional parameters may be required such as MYIP if sever has multiple network cards, or port= if the default port used by the SQL Anywhere is not free. The default port is 1498. For example:

dbsrv50 –n db_server_name –x tcpip{MYIP=server_ip_address;port=port_number}

　　For IPX running on non-Novell environment:

Determine the IPX address of the server:

Starting from SQL Anywhere version 5.5.03 onwards, one can capture the ipx address of the server machine by starting up the database server with a –Z switch :

What follows is a portion of this output using 5.5.04. Notice the line specifying Node Address: (0:160:36:204:96:148). This is the IPX address of the server.

11:40:33 Trying to start IPX link ...

11:40:33 Loading wsock32.dll

11:40:33 Trying to read property value of sademo

11:40:47 Bindery scan return code: 0

11:40:47 Sending broadcast

11:40:52 No broadcast reply received

11:40:52 No broadcast reply received

11:40:52 Server address: Socket: (18496), Node Address: (0:160:36:204:96:148), Network address: (0:0:0:2)

11:40:52 Threads started: 2

11:40:52 IPX link started successfully

Client can connect to database server using the following command line:

dbclient –x ipc{Host=ipx_address}

　　A brief description of the problem:

　　The client machine cannot locate the database server just by server’s broadcast, or because the client and the server machine are in different subnets, client cannot receive server’s broadcast of existence, and so client thinks that server doesn’t exist.

1 2 3 4 5 6 下一页