98 mchines can't find the server once VPN service is enabled.

[Philip]

HI,
I have a windows 2k server. It is running AD, DNS, DHCP
and WINS. I enabled the Routing and Remote Access for VPN
service with one NIC card(behind a hardware firewall).
The server's ip is 192.168.0.5. The VPN service grabs 10
ip's for itself(192.168.0.158-167). The Win2K and XP
workstations are having no problems accessing the server
(when pinging the server, it is pinging to the .5 IP).
But the 98 machines can't find the server, they all think
the server's ip is .158. Can some one give me some hints
on how to resolve the issue?

 

[Bill Grant]

You need to disable Netios over TCP/IP on the "virtual" interface (to
prevent it registering with WINS). This requires a registry change.

To prevent Netbt on the RRAS interface.

Open Registry Editor.
Navigate to HKLM\System\CurrentControlSet\Services (continued next line)
\RemoteAccess\Parameters\Ip

Create a new REG_DWORD called DisableNetbiosOverTcpip
Set its value to 1

After you make the change and restart RRAS, check that there are no
entries for the RRAS IP still lurking in WINS.

The W2k/XP clients will be using DNS to find the server, but W9x clients
use the Netbios name from WINS.

 

[Guest]

Thanks for your help, I will try this!

-----Original Message-----
You need to disable Netios over TCP/IP on the "virtual" interface (to
prevent it registering with WINS). This requires a registry change.

To prevent Netbt on the RRAS interface.

Open Registry Editor.
Navigate to HKLM\System\CurrentControlSet\Services (continued next line)
\RemoteAccess\Parameters\Ip

Create a new REG_DWORD called DisableNetbiosOverTcpip
Set its value to 1

After you make the change and restart RRAS, check that there are no
entries for the RRAS IP still lurking in WINS.

The W2k/XP clients will be using DNS to find the server, but W9x clients
use the Netbios name from WINS.




.