Hello
We are looking for some assistance, as Microsoft are refusing to assist even with a paid up subscription call to fix the following problem:
We are using the latest driver template written by Jim Mateer, (IMSAMP) and encountering a problem running Dialup connections via RRAS, with Microsoft, Network Browsing and resource access, i.e. (Drives, Directories).
We have remote NT4 Workstations running TCP/IP only, dialling into a RRAS server, Windows 2000. This server is connected to a Windows 2000 domain controller running WINS, and various other Workstations, where the remote Dialup Workstations require access to there resources. The RRAS server also has a WINS server, which is used to resolve the IP addresses, (see fig 1).
When the IM driver is not loaded on the remote NT4 Workstations everything works. The remote Workstations are configured with default node and have fixed IP addresses. If we install the IMSAMP driver on the NT4 Workstations it fails to indicate remote P.C. names on the “second” network. However if we manually set the IP address of, e.g. “IM_Ndiswan3” driver in the registry to the fixed IP address of the dialup device, e.g. Ndiswan3. It all works fine and under a debugger we see broadcast packets proliferate through the IMSAMP driver, without this “modification” to the registry, no broadcast packets are seen through the IMSAMP driver.
Registry Key Example, IP Address of Dial-up Workstations == 172.20.70.4
Location
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IM_NdisWan3\Parameters\Tcpip
Key’s Manually Set.
IPAddress == 172.20.70.4
SubnetMask == 255.255.0.0
Having fixed IP addresses for dial-up clients is clearly not a valid solution, in situations with DHCP. It would seem that there is some binding issue with IMSAMP, can you please advise. We have checked the driver bindings for correctness and they seem to be in order.
Additionally we have found that in order to browse, and access resources correctly, under a Domain, we have to manually enter WINS addresses into the registry, NETBT\adapters\NDISWAN3.
Note: We have an identical driver for Windows 2000, based on passthru, under this same configuration it works fine. Also all P.C.'s have the latest service packs installed.
I can not attach a file on this posting, if you need to see the picture, please send me your e-mail address and I can send it to you… ie. fig 1.
Please, Please Help
Thanks
Steve Pratt
xxxxx@bemac.com