Discussion Locked

Printer Problem and Possibly Server Comm

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We were setting up printers on a different campus. It is connected to the main campus by a T-1 line through two routers. We were setting up the printers on Novell 5.0, as non nds printers. However the printers that were set up in the tree could not be printed to. At the main campus, communication with the far campus is possible, but only after doing a find computer and inputting an ip address, or mapping the ip address in the login script. Once communication is established files can be transferred etc. Is there a problem in the set up of the server. Or is there a problem with the set up on one or both of the routers.

7 replies

by lowlytech

I am afraid before this can be answered we need more information. Are you using native TCP/IP built into NW5 or are you still using IPX/SPX. You might check for router filters, rights, queues. Another common problem that needs to be answered is werethese originally setup in bindery mode. If so you will have to educate netware 5 to recognize bindery queues. With a little more info I would be glad to lookup possible solutions.

by paul.gerth

Welcome to the world of IP ! Using IPX the server SAPs and RIPs , service and route advertisements , but with IP you either have to establish static maps using NWHOSTS on the workstations , or use a DNS and map the names of resources to their IP addresses . This won't really help with your printers unless you are using NDPS and setup the remote printers as UNIX printers . Your NDS printer definition then has the IP address of the remote LPR device , ie your remote printer . BTW make sure that you also define the gateway address on each device . This is the IP address of the router on each network that your ip host (workstation or printer) uses to get to the remote server . For what it's worth , it's the same with NT , routers don't normally forward broadcasts which browsing requires .
---paulg

by cjoego

I had the same problem at a client site,

My fix was to put static routes in the routers

This discussion is closed to new replies.