[問題] 區網內的 PC 找不到外面以 VPN 撥入的網芳 PC 嗎?

[ulimie]

下面是我的 IP 分配狀況: 192.168.1.X

WL520GU 內家用 PC/NB 全部依 MAC 設 STATIC DHCP. (2 - 6)
2 - 6 的 PC/NB 全部都在 520GU 之下.

1. WL520GU
2. PC1
3. PC2
4. PC3 用這台架 WINXP/VPN
5. NB 有線
6. NB 無線

=====

21 - 30 給偶爾外來的 GUEST 用. 這是 520GU Basic/Network/LAN 設定的 DHCP IP 範圍.

=====

192.168.1.4 那台 WINXP/VPN DHCP 設 8 - 10
NB 在外面 VPN 撥入就會取得這個範圍的 IP. 在上述例子中, 取得 9.

我會發現答案, 是因為我去看 ROUTER 裡的 Device list,
發現 NB 那張網卡 同時存在著 5 和 9, 而聯想到答案. (5 還在, 還沒消失.)
難怪用 \\NB (5) 不行, 直接用 \\new_ip_address (9) 就可以.
PC1 根本就來不及知道 NB 已從 5 改到 9 了. 總結一句話: 自己笨!

[FYI]

作者: ulimie

192.168.1.4 那台 WINXP/VPN DHCP 設 8 - 10

避開1-100 再試

[FYI]

以下是Windows Server 2003 VPN Server 的特性, 照你的敘述, 應該至少有部份吻合, 也就是VPN client sends a NetBIOS Name Query packet to the VPN server, 然而WinXP VPN Server 在接獲區網內的NetBIOS Name Query 廣播封包時, 卻不知為何沒有反應? 除非根本沒有收到來自區網的NetBIOS Name Query 廣播封包

New features for virtual private networks: Virtual Private Network - Microsoft TechNet

• NetBIOS over TCP/IP (NetBT) name resolution proxy
  
  When a remote access VPN client connects to a VPN server, it relies on DNS or WINS servers on the target network for name resolution.
  
  NetBIOS names can be resolved, without the use of a WINS or DNS server, by a VPN server running Windows Server 2003 because Windows Server 2003 operating systems include the NetBT proxy. With NetBT proxy, connected VPN clients and the nodes on network segments to which the VPN server is attached can resolve each other's NetBIOS names, as follows:

1. When a VPN client needs to resolve a name to an IP address without a configured DNS or WINS server, it sends a NetBIOS Name Query packet to the VPN server. When a node on a network segment that is attached to the VPN server needs to resolve a name to an IP address without a configured DNS or WINS server, it sends a NetBIOS Name Query packet as a broadcast on the network segment.
   
2. The VPN server receives the NetBIOS Name Query packet, checks its local cache of resolved NetBIOS names and, if the name is not found, forwards the NetBIOS Name Query as a NetBIOS broadcast on all attached interfaces, except the logical interface that is connected to all VPN clients.
   
3. The node that has registered the NetBIOS name sends a positive NetBIOS Name Query Response to the VPN server.
   
4. The VPN server receives the positive NetBIOS Name Query Response and then forwards it on the interface from which the NetBIOS Name Query packet originated to the sending node.

[FYI]

WinXP VPN Server "route print":

Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.66 20
60.xxx.xxx.xxx 255.255.255.255 192.168.0.1 192.168.0.66 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.66 192.168.0.66 20
192.168.0.66 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.66 192.168.0.66 20
192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 50
192.168.1.101 255.255.255.255 192.168.1.100 192.168.1.100 1
224.0.0.0 240.0.0.0 192.168.0.66 192.168.0.66 20
255.255.255.255 255.255.255.255 192.168.0.66 192.168.0.66 1
Default Gateway: 192.168.0.1
===========================================================================
Persistent Routes:
None

以上看得比較清楚, 不論是192.168.1.100 或設成192.168.0.100, 事實上並不在同一個網段, 此外, 小弟實驗的結果是VPN Client 只能查詢VPN Server's NetBIOS Name, 其他和反向查詢均不成功, 只能透過IP, 所以WinXP 內建的PPTP VPN Server 只有很基本的功能, 不能要求太多, 但已經夠用了