• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I'll pay you $50US if you know the answer! (About Windows 98/NT's direct connection facilities)

D

Descartes

Lifer
I know NT doesn't technically have "direct cable connection" facilities, but you can do the same thing through a standard ras connection.

I have 0 time to work on this as I'm juggling many other facets of this project already, thus I offer $50US for anyone who first responds with the answer, or a direct reference to the answer.

Background info:

- Windows 98/NT 4 as direct cable connection host (serial).
- rs232 device (pocket pc-based)

On Windows 2000, I haven't a single issue with getting this to work. Problem is, this is going to run on antiquated hardware, and I haven't the space for 2000. I've also been successful in getting this to work on Linux by way of a ppp daemon and a chat script to mimic the handshake that Windows uses, but I can't use Linux on their server. It has to be Windows 98/NT 4, thus my conundrum.

I need the rs232 device to be able to see other hosts on the same network as the server (the win98/nt 4 box). The rs232 device establishes a ppp link over the serial line by way of a "host" direct cable connection on either the 98/NT 4 box. On Windows 2000, I simply say, "allow callers to access local area network" in the connection, and I can access all other hosts on the network. On linux, I simply proxy arp the connection. On Windows 98/NT4, it simply doesn't work. I need to access an ftp server running on SCO OpenServer r5 from this rs232 device by using the Win98/NT4 box as the intermediary, serving up the direct cable connection.

Hope this makes sense. Please PM me for more details. Again, I will pay anyone $50US for the answer.

[edit]I can't use ActiveSync or any other ppp-based product like Mocha's W32 PPP because it uses the same ip for both sides of the link. This, in effect, destroys any possibility of using ftp as when the ftp server does a port command, it won't find my device.[/edit]
 
Dunno if this already solved or not 🙂 anyways, here's what I'd try:

On the NT box:

Add a modem to RAS, choose "DUN serial cable betwen 2 PCs".

Select Com port, configure the newly added pseudo modem to accept calls.

Configure network for that connection: enable TCP/IP, set auth to any inluding clear text.

Configure TCP/IP for that connection: select "Allow TCP/IP clients to access: Entire Network". IP configuration for the pocket pc device would depend on your network. Dunno if the NT box is allowed to get the pocket pc an IP via DHCP or not or if you'd be better off with a static IP... Fill in as required (I hope this part was not the root of the question -- if so I don't understand a bit and apologize 🙂).

Also check that the connection speed for the "DUN Serial Cable ..." matches a speed available on the pocket pc device.

Check with RAS admin that you have a user account for the pocket pc, that RAS is actually running and that the pocket pc user has dial in rights (good idea to have "call back" disabled to).

On the Pocket PC:

This will be rather general, I've never had to work with pocket pc devices.

Create a PPP connection via direct serial, gateway and IP probably "dynamic". User name must match the one you allowed RAS dial-in earlier. A domain and DNS IP would come in handy to.

And now the crux (which once cost me an awfull lot of sleep): make a %§$§ connection script that sends "CLIENT" (note: uppercase!) to the NT box, and nothing else.

HTH!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top