IMSAMP

NTDEV
1

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

2

Steve,

what you need is correct INF script which creates all necessary registry
info. It solves all mentioned problems, including DHCP. Unfortunately, it
isn’t documented what is necessary info and how it should look like. Misc.
drivers including tcpip.sys, netbt.sys, netbios.sys etc. expects their
configuration related to your adapters as you already found. It isn’t
enough, even RAS user mode components expect additional registry
configuration. INF script included in ImSamp example is unsuitable for this
purpose. No wonder ms refuses to assist.

I recommend to forget about NT4 and write your driver for w2k and above;
your life would be much easier. If you can’t, study INF scripts for
mentioned drivers and RAS to find out what is necessary and expected. Note
INF for our driver which tries to be as correct as possible in this mess is
about 160 kB size (no, sorry, can’t give it).

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

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\Para
meters\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 mailto:xxxxx
></mailto:xxxxx>