Network User's Guide
Table Of Contents
- Network User’s Guide
- Introduction
- IMPORTANT INFORMATION: REGULATIONS
- Table of Contents
- 1 Unix Printing
- 2 TCP/IP Printing
- Printing from Windows NT® 4.0, Windows® 2000/XP, LAN Server and Warp Server
- Overview
- Windows NT® 4.0 and Windows® 2000/XP (TCP/IP) Configuration
- Windows® 2000/XP Printing (Printer Driver not yet installed)
- Windows® 2000/XP Printing (Printer Driver already installed)
- Windows NT® 4.0 Printing
- Windows NT® 4.0 Printing Installing the Brother Peer to Peer Software
- Windows NT® 4.0 Printing Associating to the Printer
- Windows NT® 4.0 Printing Adding a Second Brother LPR Port
- Other Sources of Information
- Printing from Windows NT® 4.0, Windows® 2000/XP, LAN Server and Warp Server
- 3 Peer to Peer Printing
- 4 NetBIOS Peer to Peer Printing
- How to Print Using NetBIOS in Windows® 95/98/Me/2000/XP, Windows NT® 4.0, LAN Server and OS/2 Warp Server
- 5 Configuring Internet Printing for Windows®
- Internet Printing Installation
- Overview
- Brother Internet Print General Information
- Brother Internet Print: Configuring the Brother Print/Fax Server
- Brother Internet Print: Using BRAdmin Professional utility to Configure the Print Server
- Brother Internet Print: Using a Web Browser to Configure the Print Server
- Brother Internet Print: Installing the BIP software on Windows® 95/98/Me/2000/XP and Windows NT® 4.0
- Adding a Second Brother Internet Port
- Windows® 2000/XP IPP Printing
- Specifying a Different URL
- Other Sources of Information
- Internet Printing Installation
- 6 Novell NetWare Printing
- How to Configure Novell NetWare Printing
- Overview
- General Information
- Creating a NDPS Printer Using NWADMIN for NetWare5
- NDPS Manager
- NDPS Broker
- Creating a Printer Agent
- Configuring NetWare 3 and NetWare 4 systems
- Creating a Network Print Server (Bindery Queue Server) using BRAdmin Professional utility
- Creating a Network Print Server (NDS Queue Server) using BRAdmin Professional utility
- Creating a Network Print Server (NDS Queue Server) using Novell NWADMIN and BRAdmin Professional utility
- Creating a Network Print Server (NDS Remote Printer) using Novell NWAdmin and BRAdmin Professional utility
- Other Sources of Information
- How to Configure Novell NetWare Printing
- 7 Printing from a Macintosh®
- Printing from a Macintosh® Using AppleTalk® and TCP/IP or Simple Network Configuration capabilities
- Overview
- Macintosh® Configuration (Mac OS® 8.6 - 9.2)
- How to Select the Print Server (AppleTalk/EtherTalk)
- How to Select the Print Server (TCP/IP)
- Macintosh Configuration (Mac OS® X 10.1-10.2.1 or greater)
- How to Select the Print Server (AppleTalk/EtherTalk)
- How to Select the Print Server (TCP/IP)
- Changing the Configuration
- Other Sources of Information
- Printing from a Macintosh® using Simple Network Configuration capabilities of Mac OS® X
- Printing from a Macintosh® Using AppleTalk® and TCP/IP or Simple Network Configuration capabilities
- 8 DLC Printing
- 9 Web Based Management
- 10 Front Panel Setup Menu
- 11 TCP/IP Configuration
- Assigning TCP/IP Information
- Overview
- Using the machine control panel to allocate an IP address (Models with LCD panels only)
- Changing the IP Address using the BRAdmin Professional utility
- Using BRAdmin Professional utility and the IPX/ SPX Protocol to set the IP address
- Using BRAdmin Professional utility and the TCP/ IP Protocol to set the IP address
- Using DHCP to Configure the IP address
- Using APIPA to Configure the IP Address
- Using ARP to Configure the Print/Fax Server IP Address
- Using RARP to Configure the IP Address
- Using BOOTP to Configure the IP Address
- Assigning TCP/IP Information
- 12 Internet FAX (MFC Only)
- 13 Troubleshooting
- Overview
- Installation problems
- Resetting the Print/Fax Sever back to factory settings (Test Switch)
- Intermittent Problems
- TCP/IP Troubleshooting
- UNIX Troubleshooting
- Windows NT® 4.0/LAN Server (TCP/IP) Troubleshooting
- Windows® 95/98/Me Peer to Peer Print (LPR) Troubleshooting
- Windows® 95/98/Me Peer-to-Peer (HP JetAdmin compatible method) Troubleshooting
- Windows® 95/98/Me/2000/XP and Windows NT® 4.0 Peer-to-Peer Print (NetBIOS) Troubleshooting
- Brother Internet Print (TCP/IP) Troubleshooting
- Windows® 95/98/Me/2000/XP IPP Troubleshooting
- Novell NetWare Troubleshooting
- AppleTalk Troubleshooting
- DLC/LLC Troubleshooting
- Web Browser Troubleshooting (TCP/IP)
- Internet Fax Troubleshooting
- 14 Brother Internet Fax Printing Software
- Appendix
- INDEX
TROUBLESHOOTING 13 - 2
2
If the configuration page prints but you cannot print documents,
try the following
a
If you are using TCP/IP:
Try pinging the Print/Fax server from the host operating
system command prompt with the command:
ping ipaddress
Where
ipaddress
is the Print/Fax server IP address (note
that in some instances it can take up to two minutes for the
Print/Fax server to load its IP address after setting the IP
address). If a successful response is received, then proceed
to the UNIX, TCP/IP Windows NT
®
4.0/LAN Server,
Windows
®
98/95/Me Peer to Peer (LPR), Internet Printing or
Web Browser troubleshooting section. Otherwise, proceed to
step 3, and then go to TCP/IP Troubleshooting section.
b
If you are using Novell system:
Verify that the Print server can be seen on the network. To do
this, login as the SUPERVISOR (not as someone with
supervisor privileges) or ADMIN (for Netware 4 or later
servers), go into PCONSOLE or NWADMIN, select PRINT
SERVER INFORMATION, and select the name of the Print
server (make sure that you have entered the Print server
name). If you can see
Print Server Status and
Control
in the menu, then the Brother Print/Fax server is
visible to the network, proceed to the Novel NetWare
Installation Troubleshooting Section. Otherwise, go to step 3.
c
If you are running AppleTalk for Macintosh:
In case of using Postscript driver make sure that you can see
the Print/Fax server name under the LaserWriter 8 icon in the
Chooser. If it is visible, then the connection is good, so
proceed to the AppleTalk for Macintosh Section. Otherwise,
go to step 3.
If none of the following steps are successful, there is almost
certainly a hardware or network problem!