The computer with the modem or ISDN-Card
I call 'server', the other 'client'.
I assume that the IP of the server
is
192.168.1.1 and the IP of the client is 192.168.1.2. Please
install WinProxy, NAT32 or whatever else first. If they work, UseDUN should
work too.
On the server you have to start UseDUN with the parameter /server and an IP number from which
it accepts commands (pure text compare 'from left' - no IP mask!):
usedun /server /192.168.1
Using these params it would accept commands from 192.168.1.x but also from 192.168.123.x.
You will not see anything - it waits in the background for a message from another UseDUN on an other maschine.
To close the previous started server use the parameter /close:
usedun /close
To create a DUN connection from a
client you need the IP of the server, e.g. 192.168.1.1 and the name of
the DUN connection, e.g. "My Provider" (the qoutes are needed).
To connect:
usedun /connect:"My Provider" /192.168.1.1
On the server you should disable
'prompt before dialing' in the DUN settings. If it is enabled somone has
to confirm the connection on the server (Win9x). On NT4 and Win9x the password
has to be saved for the connection even it's not so good for security...
And to disconnect:
usedun /disconnect /192.168.1.1
The first found active DUN connection will be disconnected.
Problems:
If you get an error message "runtime
error 50003" or "31037", UseDUN tries to load a wrong version
of the MSWINSCK.OCX. To ensure that UseDUN loads the OCX you got
with it, create a link to the UseDUN.EXE with the folder of UseDUN as working
directory.
If this doesn't help you can try to register the MSWINSCK.OCX manually using
REGSVR32. Assuming UseDUN and MSWINSCK.OCX are in the folder C:\Program Files\UseDUN
the command to register it is:
REGSVR32 C:\Program Files\UseDUN\MSWINSCK.OCX
|