Member Avatar for tofun.007

Hello

I have one problem with network.
Please help me.

Description :
I be going to running a network.
The operation system of clients is MS-DOS and they should connect to the server novell that ,is in other place. by one commeunication line (dial/up , P2P)

For this porpost I use of two computer that thems operation system are windows server 2003 that they have used for running VPN server.

I have use of netware clients for windows for commiunicate of windows with novell.
I have run the services DNS , DHCP , WINS and RAS in windows server for running VPN server.

Problem :

  1. What is protocol that use for connect Dos to Windows ? (TCP/IP or IPX)
  2. What is configuration of Dos for introduce to Novell that ,is in other place ?
  3. What is configuration Windows server for make commiunication between Dos and Novell ? (configure VPN server)

please look at this image :

Please Help me about this problem.
Thanks for Your guide.

  • 3 Contributors
  • 4 Replies
  • 194 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by JamesM

Dani AI

Generated

Two realistic ways to solve this are: 1) make the remote DOS workstations effectively part of the NetWare network across the link so the NetWare client can talk to the server natively, or 2) avoid carrying the NetWare client across the slow/dial link and have users connect to a host on the server side (remote session/terminal). Each has pros and cons; choose by how many clients you have and how fast the link is.

If you want native access across the link:

  • Use a site‑to‑site approach (routers or VPN gateways) so the remote subnet is routable to the NetWare server without NAT or protocol translation. Do not hide client addresses behind NAT — that breaks many NetWare services.
  • If the NetWare environment uses a legacy transport that the link/routers won’t carry, you’ll need either L2 bridging or a tunnel that supports that protocol (IPX-over-IP, etc.), or enable the server’s TCP/IP‑based access if the server supports it.
  • On the VPN/gateway, allow the NetWare traffic through the firewalls and check routing so the server sees the client IPs directly.

If you want to avoid protocol headaches:

  • Put a Windows host on the server LAN with the NetWare client installed, and have remote DOS machines use a remote session (RDP/Terminal Server or a screen‑sharing tool). This reduces bandwidth and complexity and is often easier on slow links (as pointed out).

Quick troubleshooting checklist:

  • Verify client IP, netmask and gateway are correct.
  • Confirm basic reachability (ping/traceroute) from each side (as suggested).
  • Inspect VPN/firewall logs and capture traffic on the server side to see whether packets arrive.
  • If dial‑up PPP is used, verify the link actually carries the transport you need (IPX over PPP is not always supported).

If more details about the NetWare version, exact VPN type, or the link (dial/P2P) are provided, a tighter step‑by‑step configuration can be given.

Recommended Answers

All 4 Replies

Member Avatar for JoetjeF

What version of NetWare are you running? Can you ping the NetWare server from your DOS clients?

Member Avatar for tofun.007

What version of NetWare are you running? Can you ping the NetWare server from your DOS clients?

Hi
I use of:
Novell Client 4.91 SP3 English.exe

Member Avatar for tofun.007

Dos doesn't ping netware server.
becuese i don't configure dos. (getway)
and i running TCP/IP protocol in dos not IPX.

How introduce Novell server to Dos ?

Member Avatar for JamesM

In this day and age, all your remote computers should be running windows. That said, it is still possible to make DOS based computers do useful work.

To connect DOS to a novel server you need to run the DOS client for Netware setup. It is simpler if the server is running XP but can be done with TCP/IP.

I have no idea why you are trying to gateway the dos through two windows computers to the netware server. This sounds nuts, difficult and slow.

If the computers are remote with a communication link running between two locations then I recomend you use routers on each end, possibly setting up a VPN between them. This will make it seem to the DOS workstations that they are on the same network as the server.

If the link is slow, then I suggest you have the remote DOS boxes connect to other computers that are local to the server via a PC-Anywhere or similar session. It will require one computer on the servers network for each computer that needs to come in remotely. This will allow applications to run with speed, since only the screen and keyboard codes go back and forth accross the link. Just as fast as being there.

If you hare more than 2 or 3 remote computers than setting up one Windows Terminal Server on the servers network will allow multiple remote computers to connect and run applications without having a computer on the host/servers network for each one.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.