Sharing Com Ports

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

OK,

I already know the answer is upgrade the software, but I can't, so we have
to go through this process.

I have a client who has a restaurant software application that runs under
DOS. Until recently, he used a lantastic network that ran without a problem
for almost 10 years. We have just installed his new Windows 2003 server and
discovered a problem. We need to share the serial ports to allow more dos
printers to be used. Under NT this was possible and I know under SBS200 you
could set up a similar thing using modem sharing.

Is there some software that allows to share a serial printer using dos
commands??

Thanks

Brandon Hegh


.

Relevant Pages

  • Re: TCP/IP comms problems between WinXP and DOS
    ... I have written client and server versions ... In the instance where I have a problem the DOS system is running as client, ... By simple changing of i/p addresses / network names I have run the client ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Ram Disk by arsoft didnt work.....
    ... Last time I worked with MS DOS Network Client many, ... usually does not help you much with troubleshooting network problems. ... > name and workgroup (start wizard). ...
    (microsoft.public.windowsxp.embedded)
  • Re: freeBSd for a 486
    ... Have you maybe thought of DOS + Arachne? ... client included, serves as a file manager, and even ... Yep p3-733 here had a Novell DOS7 partition with yan and arachne setup and able to ... David Lord - david@xxxxxxxxxxxxxxxxxxxx ...
    (comp.unix.bsd.freebsd.misc)
  • Re: dos - > samba , is possible?
    ... > I need access to samba serwer on freebsd from some dos terminals. ... There is a Microsoft Network Client for DOS available for free download ... At the time when I was an OS/2 fun and had a Warp Server of my own I ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Blocking port automatically
    ... It can be used for a dos, ... handshake between the client and the server. ... the attacker is on the same local network as 172.27.5.39, ...
    (Fedora)