Nortel NAM 4 - Cannot connect... 2

[jchoponis]

I have a refurbished nortel applications module (NAM) v 4.1 that runs my voicemail.

I have the nortel software to interface with it via tcp/ip, but i am unable to connect. the ethernet interface does light up and have activity when plugged in.
I have been having a lot of trouble finding information about how to check the tcp/ip config on the nam - i have hooked up a monitor and keyboard to it and can tell that it runs OS/2 3.1 and that the ethernet interface is enabled in the bios.

i cannot seem to get to the command line - right after boot up, i see the c:\ prompt, but the os continues to load os2you 3.2 "limited host interface...". It says use ctrl + break to exit, but those keys do nothing....

Any ideas would be great...this older nortel stuff has been a real bear...

 

[lugerlover]

tcpcfg at prompt

 

[exsmogger]

Login to F915 on the NAM and add the Monitor package. Reboot the NAM and you will then get the regular OS/2 window.

Brian Cox

http://www.jandjcommunications.com

 

[jchoponis]

I have tried f915 - it says inactive feature.

 

[jchoponis]

Thanks for the quick reply - this form has already been more helpful than experts exchange...

 

[jchoponis]

Update - I found another thread that suggested trying sequential f9xx - f922 came up with the prompt.

A new wall...i found the where to show the monitor package, but i am prompted for another password...can't seem to crack that one.

ACCESS2 doesn't work...

 

[exsmogger]

SVGANEEDED

Brian Cox

http://www.jandjcommunications.com

 

[jchoponis]

YES! That was it. I could not find that in any of my manuals - have never seen that password...but it worked...


Now i am rebooting it to see if i can do the tcpcfg command from the os/2 cmd line now.

Thanks much exsmogger!

 

[jchoponis]

Ahhh! I changed the ip via the os/2 interface - but the software still will not connect - i can't even ping the nam still!

 

[jchoponis]

I have checked the interface - it is enabled and has a link and activity lights.

 

[lugerlover]

did you reboot after change was made

 

[jchoponis]

Yes. I have rebooted serveral times after enabling/disabling the interfaces many times....

I cannot even ping the loopback when I enable it. I am wondering if the driver for the NIC was not installed/configured correctly? Could that happen, or does OS/2 auto config devices (it says it's os/2 warp 3).

Sorry if a dumb question - i am "new" to the "old" os/2...

 

[exsmogger]

From an OS/2 window run the MPTS program. You'll be able to see the driver and protocols installed, as well as the current IP address.

Brian Cox

http://www.jandjcommunications.com

 

[jchoponis]

OK. Thanks. I will try this.

 

[jchoponis]

I tried mpts.

Current config shows:
ibm paralle port
0-ibm os/2 netbios
0-ibm tcp/ip

I changed the 0 to a 1 on ibm tcp/ip and rebooted - now i can ping my address and the loopback! But i cannot ping anything else...thought it might be a swtich auto negotiation, so i hooked it up to a small hub - no change...

 

[jchoponis]

found something that may help - behind the "taskbar" thing, there are several minimized cmd windows hidden - found one that showed something about TCPSTART.CMD.

below a sample of the window:

SEE IF INSTALL CLEANUP IS NEEDED
...
[adds default route to route table]
...
MAKE CURRENT CONNECTION LAN ONLY
STARTING TCP/IP PROCESS
INET DAEMON STARTING
SENDMAIL STARTING
...

Does this mean that my adapter is loaded correctly? I am baffled about why I cannot ping the NAM or ping any computer from nam, but i can ping the nam itself...any ideas would be much appreciated.

 

[lugerlover]

per ITAS

Network Interface Card Customer Recommendations


Recommendations

1. Background

The Norstar Applications Module (NAM) is the server platform for Norstar applications products including Voice Mail, Interactive Voice Response (IVR), Automated Call Distribution (ACD), Dial-By-Name (DBN) and TSAPI. With Norstar Voice Mail (NVM) 3.0 and IVR, networking is being introduced which allows the user to make use of Local Area Network (LAN) and Wide Area Network (WAN) data communications technology.

A Network Interface Card, or ÈNICÉ, must be installed in any NAM to enable its connection to a LAN/WAN. There are over 30 companies supplying network cards for data communications and no plans exist at this time for Nortel to re-sell them, or to develop a NIC itself. With scores of cards to choose from, customers of Norstar applications products wishing to benefit from the networking capabilities will need help in selecting an appropriate card and in making the NAM operational with the NIC.

The purpose of this Product Description is to provide a list of NICÉs that have been tested for use in the NAM platform, along with additional information that will help the user install the card and ensure it operates properly.




Figure 1: Example of a Computer Adapter Card.



2. Recommended Cards & Test Configuration

The following NICÉs have been tested by Nortel and third party groups and perform satisfactorily in the NAM platform. This list is not an exhaustive list of cards that might work in the NAM. The user is directed to the Internet web site "

http://www.austin.ibm.com/pspinfo"

for a list of NICÉs that are compatible with the OS/2 WARP 3.0 operating system used within the NAM.

2.1 Recommended Cards Í Ethernet

NOTE: Only ISA cards can be used in NAM I systems. For the NAM II, PCI cards are recommended for ease of installation.

BUS
Supplier
NIC
Model No.

ISA
3COM EtherLink III 3C509B
3COM Fast EtherLink 3C515
Hewlett-Packard DeskDirect 10/100VG J2573A
PCI
3COM Fast EtherLink XL 10/100 3C595-T4
3COM Fast EtherLink XL 3C905-T4
D-LINK Ethernet DE-530CT
GVC 10BaseT PNP 2006BT
Hewlett-Packard DeskDirect 10/100VG J2585A
IBM Pro 100/10 EtherJet 86H2432
Intel EtherExpress Pro 100 PCLA8465B
MaxTech 10/100 Combo NX-110PCI

2.2 Test Configuration

The NICÉs were tested in a NVM 3.0 Model 2 NAM II system with NVM 3.0. The telephony middleware was ACCESS 2.6 and the operating system was OS/2 WARP Connect 3.0.

The test procedure in each case was:

The NAM was configured in "Headed" mode, with a video card, monitor, keyboard and mouse installed.
After shutting down the NAM, the NIC being tested was installed in the appropriate expansion card slot. For PCI cards, slot 1 closest to the Hard Disk Drive dock was used. For ISA cards slots 8, 7, 6 or 5 were used, depending on which was available. The NAM was powered back up in Presentation Manager mode.
The NIC driver was installed by running MPTS.EXE (in OS/2 WARP Connect), choosing "Other Adapter" from the menu and directing the software to search the floppy disk drive (drive "A:") for the proper installation files. (The installation disk that comes with the NIC was used.)

The NVM 3.0 networking function was setup by running TCPCFG.EXE (in OS/2 WARP Connect) to configure the local IP address, default gateway and domain name services.
Once the networking hardware and software was installed, the NAM was rebooted without any disks in the floppy disk drive until the ascending tones signal correct operation of NVM.
The following networking tests were performed: PING the internal IP address; PING the local

http://WWW server;

FTP a file from the local FTP server; and HTTP a web page from the Internet.


3. Considerations, Precautions & Site Requirements

3.1 Considerations

The engineering rules of the NAM platform impose some limitations and restrictions on the use of NICÉs:

If the NIC is being installed on a NAM I, only an ISA NIC can be used. If the NIC is being installed on a NAM II, either an ISA or a PCI NIC can be used.
The interrupt (IRQ) setting designated for NICÉs is IRQ 9. If the pre-set configuration has been changed for any reason, reconfigure any other devices that may be using IRQ 9 to another IRQ and ensure the CMOS is configured to have IRQ 9 available for NICÉs.
If the NIC is an ISA "Plug-and-Play" card, the "Plug-and-Play" feature must be disabled. If it isnÉt, a conflict with the requirement for using IRQ 9 occurs that prevents a "Plug-and-Play" card from being recognized.
There are limitations to which expansion card slots may be used for the NIC. Using a PCI Bus NIC is recommended and should be installed in slot 1 next to the Hard Disk Drive dock in the NAM.
ISA Bus NICÉs may be used and placed in an available ISA slot from slot 5 through 8.
The operating system of the NAM I is OS/2 2.1. The operating system of the NAM II is OS/2 WARP Connect 3.0. Only NICÉs that have OS/2 drivers (or NDIS for OS/2) will work on the NAM platforms.
At this time, installation of a NIC cannot be performed without the presence of a video (SVGA) card in the NAM and a monitor and keyboard (mouse optional) attached. The NAM must be configured in "Headed" mode. (In the NAM II, to activate the video card dip switch #8 must be set to OFF on the Single Board Computer (SBC) card.) Once installation is complete, it may be reconfigured into "Headless" mode, as required at the site. (In the NAM II, the dip switch #8 on the SBC must be set back to ON.) (For the NAM I: Norstar Voice Mail 2.1 Maintenance Manual, P0857707 English, P0857708 French; "Monitor, Keyboard and Mouse", pp. 3-38 to 3-41. For the NAM II: Norstar Applications Module II Installation and Maintenance Manual, P0869547 English, P0869548 French; Issue 01, "Monitor, Keyboard And Mouse": pp. 71-79; Issue 02, "Adding And Removing A Monitor, Keyboard And Mouse", pp. 87 to 96.)

3.2 Precautions

It is recommended that a NIC from the list above be used for implementing the networking capabilities of the NAM. It has been found that not all NICÉs supported for OS/2 operate properly on the NAM. In particular, any "Plug-and-Play" cards must have this feature disabled or they are not useable. All the standard precautions concerning handling of printed circuit boards and avoiding electrical discharges apply to the NICÉs.

It is recommended that a network administrator, network technician or IS/IT person perform the installation steps, or provide assistance. The networking functions of the NAM cannot be set up without obtaining the proper IP address, gateway and domain name services information for the LAN/WAN to which the NAM will be attached.

There are three types of Ethernet network cabling that the user may encounter, each with its own connector to the NIC. Twisted Pair copper cable usually has the rectangular RJ-45 connector. Coax cable has the BNC connector. Fibre optic cable uses a fibre optic connector. Obtain a card with the correct connector.

3.3 Site Requirements

To be successful in installing and using a NIC from the recommended list above:

Buy the card new and ensure the installation disk coming with the card is available for installation.
The NAM networking function must be set up with the NAM configured with its own local IP address. The gateway IP address, domain name server IP address, and fully-qualified domain name for the NAM are not absolutely required, but should be configured if available. If not, the NAM IP address may be used as the default gateway IP address.
If installing a monitor package on the NAM I, the procedure in the Norstar Voice Mail 2.1 Maintenance Manual must be followed.
If installing a monitor package on the NAM II, the procedure in the NAM II Installation and Maintenance Manual must be followed. To activate the video card, dip switch #8 must be set to OFF on the Single Board Computer (SBC) card in the NAM II. It is recommended that the approved SVGA video card (which is described in the Norstar Product Catalog) be used as it is 100% compatible with the NAM.


4. Customer Support

The first line of support for the user once the NIC has been installed, or if a problem is encountered during installation, is the network administrator, network technician or IS/IT support person for the userÉs organization. It is recommended that one of these individuals be involved in the installation.

The next line of support is the network interface card supplier/manufacturer. Most suppliers maintain Internet WEB home pages with product support sections. The user is in many cases able to locate and down load drivers and fixes to specific problems from such WEB sites. The user can also obtain assistance through the reseller of the card or by contacting the supplier directly. IBM supplies some information and fixes related to the OS/2 WARP Connect 3.0 operating system through its WEB sites. In addition, there are many OS/2 user groups that can be contacted through the World Wide Web.

Should performance of the Norstar Application Product on the NAM be affected after the NIC has been installed or during installation, NorstarÉs Customer Support ITAS group may be contacted. They must be alerted to the fact that a network interface card has been installed and the user seeking help must be prepared to give all the information about the choice of NICÉs and the installation procedure used.

Nortel does not design and manufacture network interface cards and does not sell or support NICÉs. It is recommended that a NIC from the list above be chosen. If the user chooses any other card, Nortel may not be able to provide assistance to the user in solving network problems.



5. Appendix

5.1 OS/2 NIC Installation Procedure

The following procedures are used to install an Ethernet NIC in a NAM under OS/2. Please note that a keyboard, monitor, and mouse are required to perform this operation.

This is a technical procedure and should only be attempted by trained technical personnel.

Ensure that all safety rules are followed and the NAM is unplugged before installing/removing any card. Please wear a grounding wrist strap before servicing any internal components on the NAM.

Drivers for each card are supplied on a diskette which comes with the card. Here are the directories for each cardÉs driver:

Supplier
NIC
Driver Directory

3COM 3C509B \NDIS2\OS2
3COM 3C515 \NDIS\OS2
Hewlett-Packard J2573A \NDIS2
3COM 3C595-T4 \NDIS2\OS2
3COM 3C905-T4 \NDIS2\OS2
D-LINK DE-530CT \NDIS\OS2*
GVC 2006BT \NDIS\OS2
Hewlett-Packard J2585A \NDIS2
IBM 86H2432 \
Intel PCLA8465B \NDIS
MaxTech NX-110PCI \NDIS2\OS2

* Special Requirement - Extract file "Files2.arj" onto a blank formatted diskette first. Look for the directory on this diskette.

5.2 Installation of the NIC (PCI Card)

Note: Installation of PCI NICÉs does not apply to NAM I platforms.

Locate PCI slot #1 on the main backplane board and using a Philips screwdriver remove the back spaceholder and gently insert the PCI NIC.
Once the NIC is installed in the NAM, secure with Philips screw and replace all covers and screws.
*Note: IRQ 9 MUST be made available for the PCI bus. This is pre-set on the systems. PCI cards are auto-configuring and do not require manual configuration at the hardware level.
Proceed to section 5.4 Configuring the NIC under OS/2.
5.3 Installation of the NIC (ISA Card)

Locate a free ISA slot on the main backplane board and using a Philips screwdriver remove the back spaceholder and gently insert the ISA NIC.
Once the NIC is installed in the NAM, secure with Philips screw and replace all covers and screws.
*Note: IRQ 9 MUST be made available for the NIC. If it is not available, reconfigure any other devices that may be using IRQ 9 to another IRQ.
5.3.1 Configuring the NIC (ISA)

Shut down the NAM as per operating instructions and insert a DOS bootable diskette in drive A:
Once the system is rebooted in DOS mode, insert the NIC configuration diskette into drive A: and follow the directions according to your specific NIC.

5.3.1.1 HP 2573A ISA Adapter

After inserting the diskette labeled HP Support Disk for J2573A Rev A.05.00 (or later) type HPVGSET from the A: prompt and press return.
From the Main Menu, select Manual Configuration and set the following options:
Interrupt LevelIRQ 9(Edge)
I/O Address Range300-31FH
Boot ROMDISABLED
I/O or Memory MappedI/O Mapped
LAN ConnectorAuto Select
Next, exit the configuration menu, and select Save Configuration To Card and exit program.
Proceed to section 5.4 Configuring the NIC under OS/2.
The location for the OS/2 Driver files is A:\NDIS2
The driver name is HP DeskDirect 10/100 ISA LAN Adapters

--------------------------------------------------------------------------------

5.3.1.2 3Com 3C509B-TP ISA

After inserting the diskette labeled 3COM Etherdisk type 3C5X9CFG from the A: prompt and press return.
From the Install Configure NIC menu, select the following options:
I/O Base Address300
IRQ 9
Boot PROMDisabled
Transceiver TypeAutoselect
Network Driver OptimizationWindows or OS/2 Client
Plug and PlayDisabled
Full DuplexDisabled
Select OK from the menu to save the settings and exit program.
Proceed to section 5.4 Configuring the NIC under OS/2.
The location for the OS/2 Driver files is A:\NDIS2\OS2
The driver name is 3COM Etherlink Family OS/2


--------------------------------------------------------------------------------

5.3.1.3 3Com 3C515 ISA

After inserting the diskette labeled 3COM Etherlink 2.0 (or later) type
3C515CFG configure /bsize:disabled /int:9 /port:300 /dma:6 /TR:auto /optimize:normal /fullduplex:disabled /nopnp
This will configure the NIC for these values:
I/O Base Address300
IRQ 9
Boot PROMDisabled
Transceiver TypeAutoselect
Network Driver OptimizationNormal
Plug and PlayDisabled
Full DuplexDisabled
Proceed to section 5.4 Configuring the NIC under OS/2.
The location for the OS/2 Driver files is A:\NDIS2\OS2
The driver name is 3COM Fast Etherlink Bus Master OS/2

--------------------------------------------------------------------------------

5.4 Configuring the NIC Under OS/2

Configure the NAM for "Headed" (keyboard and monitor) mode as per maintenance manual (see reference in Section 3.1 item 7). In the NAM II to activate the video card, dip switch #8 must be set to OFF on the Single Board Computer (SBC) card.
Reboot NAM and wait until OS/2 Presentation Manager screen appears.
Click on the OS/2 Window icon from the OS/2 LaunchPad.
From the OS/2 Prompt type "MPTS" and press <<ENTER>>.
At the MPTS menu, click on "CONFIGURE".
Select "LAN Adapters and Protocols" and click "CONFIGURE".
Remove all existing devices and protocols.
Insert the diskette that came with your network card into drive A:
From the "Adapter and Protocol Configuration" screen, Click on the "OTHER ADAPTERS" button.
. Enter the full path of the OS/2 Drivers for this NIC (see the list in Section 5.1). If you do not know the full path of the network drivers, consult the driver documentation or close the MPTS program and locate the driver directory on the diskette and restart MPTS.
. Once the system has copied the drivers to the hard disk drive, located the new driver entry from the Network Adapters list, select it with the mouse and press the "ADD" button.
. Next, from the "PROTOCOLS" window, select any protocols you wish to have bound to this adapter and click on the "ADD" button. The only protocol required for NVM 3.0 is IBM TCP/IP.
. Once all the protocols have been added to the adapter, click on the "OK" button to configure.
. Click on the "CLOSE", then "EXIT" buttons to exit MPTS.
. Ensure the "UPDATE CONFIG.SYS" button is checked, and click the "EXIT" button to finish.
5.5 Configuring TCP/IP for NIC

Once you have successfully configured the NIC, to configure the TCP/IP, type TCPCFG from the OS/2 Prompt.
At the main TCP/IP Configuration Screen, select the network adapter number you have just configured in MPTS. If you added an adapter as #1 (Numbering starts at 0, so the second card would be #1) then select LAN Interface #(card number) and ensure the Enable Interface button is selected.
Enter all the information required in the IP Address, Subnet Mask, Routing and HostNames (fully-qualified domain name) fields. . Enter the name of the NAM and its IP address in the Host Name Configuration, as well as entries for other remote NAMs not defined in any Domain Name Server (if any exist). Once complete, close the TCP/IP configuration program and ensure you select to SAVE the changes if necessary. Verify that Ultimail does not autostart.
Once the system is configured, attach the appropriate network cable to card and reboot the NAM.
To test the TCP/IP connectivity, make a note of the TCP/IP address for the NAM you have just configured, and from a remote station which is configured with TCP/IP run a PING program and enter this IP address. If there is a response from the NAM, then the configuration is valid. On the NAM, open an OS/2 window and Ping the NAMÉs own fully-qualified domain name Í it should respond with its IP address. Any other similarly-configured NAMÉs on the network may be Pinged from this NAM, using their own fully qualified domain name.
5.6 Finishing Up

If there are no errors reported while booting the NAM and if TCP/IP is installed and Pinging it is successful, the NAM may be reconfigured to "Headless" mode, as required at the site, as per maintenance manual (see reference in Section 3.1 item 7). In the NAM II, the dip switch #8 on the SBC must be set back to ON. If the NAM was already operating in "Headed" mode, then no further operations are necessary.

5.7 Glossary & Terms

ACCESS
Telephony middleware developed by Nortel for running telephony application software such as NVM, IVR and ACD.

Address Mask (Subnet)
A 32-bit long mask used to strip off the first part of an IP address leaving the remainder for subnet addressing. Consists of a string of binary ones (corresponding to the network/subnetwork component) followed by a string of binary zeros (corresponding to the host component). Router software will perform a boolean AND operation between the address mask and the incoming IP address to isolate the host component for indexing into a routing table.

Boot
To turn on a computer and cause it to start executing the basic startup software usually housed in the Basic Input/Output System (BIOS). The term comes from the word bootstrap.

Bootable Disk
A diskette that contains the necessary part of the operating system so the computer can boot up.

Bus
The electric connection linking the electronic devices such as the internal sections of a computer (i.e. the CPU, expansion cards and peripherals).

CMOS
Complimentary Metal-Oxide Semiconductor - a device used for RAM and switching applications. CMOS settings may be changed in the Setup of the computer.

Domain Name
The identifying title of a system of computers, usually including the top domain and all its subdomains, e.g. nortel.com

Domain Name Server (DNS)
A central computer connected to all other computers in a domain or subdomain and connected to the Internet, which translates domain names into IP addresses and IP addresses into domain names. The DNS directs information to and from the domain computers and computers on the Internet

Driver (Device)
A program that allows a hardware peripheral, known as a device - such as a NIC - to communicate with the computer.

Ethernet
A widely used LAN protocol that is the original Carrier Sense Multiple Access/Collision Detect (CSMA/CD) LAN that lets PCs listen for pauses before they ÈspeakÉ. Ethernet LANs use coaxial cable or twisted pair wiring for connecting computers.

Fully Qualified Domain Name
The combination of host name and domain name, e.g. mycomputer.nortel.com

"Headed"
A computer containing a video card with the monitor, keyboard and mouse connected. This would be the normal configuration of a computer. The majority of NVM systems are not "Headed". All ACD bundled systems come with a monitor package and are "Headed" systems.

"Headless"
A computer without a video card and without the monitor, keyboard and mouse attached. This is ÈnormalÉ mode for NVM systems.

Host Name
In networking, the name of a computer that primarily provides services, such as database access, to other computers in the domain. The host name is associated with a unique IP address. Since the NAM has a unique IP address, it qualifies as a host.

Internet
A global TCP/IP network linking millions of computers for communications purposes.

Interrupt (IRQ)
A command that tells the CPU to stop what it is doing and wait for further instructions. IRQ - Interrupt Request Line.

An IRQ is a separate communication line within the computer that runs from hardware components to the CPU which is reserved for use by an interrupt signal. IRQs are prioritized within the computer according to the importance of each device.

IRQ Conflict
Means that two devices are vying for same IRQ. On installation of a device where an IRQ conflict occurs, the user may have to manually configure the IRQ settings to resolve the conflict.

IS/IT
Information Systems/Information Technologies - a section of an organization that looks after the computer technology used by the organization.

ISA
Industry Standard Architecture - the standard 16-bit Bus modeled after IBMÉs original 8-bit PC Bus.

LAN
Local Area Network - a group of computers physically connected in a manner that lets them communicate and interact with each other.

NAM
Norstar Applications Module - an industrial-grade computer server platform for Norstar application products that connects with Norstar Key Switched Unit telephone systems.

NDIS
Network Device Interface Specification.

Networking
The sharing of storage devices, peripherals and applications between computers that are networked together.

NIC
Network Interface Card - an adapter card, inserted into a slot in the computer, containing the hardware necessary to connect a computer to a network.

OS/2 Launchpad
An icon on the OS/2 window that contains objects and push buttons for commonly used actions.

OS/2 WARP Connect 3.0
The operating system produced by IBM for a personal computer. 3.0 is the release version. Connect provides the networking portion of the operating system and includes the executable programs MPTS.EXE for installing the NIC driver and TCPCFG.EXE for configuring TCP/IP.

Path
The route the computer needs to take to find, store and retrieve a data file. The path starts with the drive letter designation: "A:" for the floppy disk drive.

PCI
Peripheral Component Interconnect - the Intel local Bus standard that allows for faster communication between the computerÉs CPU and peripheral components.

PING (Packet InterNet Groper)





Protocol
A program used to test access to an address by sending an echo request and waiting for an echo reply. The term is used as a verb: "Ping host X and see if it's up!"

A set of rules and procedures for exchanging data between computers on a network or through the Internet.

Reboot
To restart the computer and operating system.

Routing
The path a message takes from its point of origin to its destination on a network or the Internet.

Single Board Computer (SBC)
Computer main boards for industrial grade computers containing the CPU, RAM memory, chipset and BIOS. SBCs are designed to insert in to a backplane board with expansion card slots and offer more reliable, rugged designs than the main boards for PC computers.

Subnet Address
An extension of the IP addressing scheme that allows a single IP network address to represent multiple physical networks. Accomplished by dividing the local (Host) part of the address into two fields to represent the subnetwork and the Host. This subdivision of the address is not visible to external networks.

TCP/IP
Transmission Control Protocol/Internet Protocol - a language governing communication among all computers on the Internet.

TCP protocol checks packets of information for errors, submits requests for re-transmission in the event of errors and returns multiple packets of a message into the proper original sequence when the message reaches its destination.

IP dictates how packets are sent out over networks and has a packet addressing method that lets any computer on the Internet forward a packet to any other computer that is a step or more closer to the packetÉs recipient.

WAN
Wide Area Network - a collection of computers connected (or ÈnetworkedÉ) to each over long distances, typically using common carrier facilities (Source Í IBM).

 

[jchoponis]

Thanks for you help guys - I believe I will need to crack the case - so I am getting some help from a wholesale company that refurbishes these things.

I believe something was misconfigured or left out altogether when it was refurbished by their company.

Will post what I find. Thanks again for your help thus far.

 

[curlycord]

Are you connecting via switch/hub or direct? if direct are you using crossover cable?

What version is the software you have for NVM?

Is NVM enabled in F983 option 44/view? I think in 4.1 it is but check anyway.

Pull the network card out and see what make it is.

 

[jchoponis]

I am hooked up via hub. I have also done direct via x-over.

NVM software is version 4.0 that came with nortel remote utilities version 11.

F983 and a 44 option - a show shows me that I have 8 ports.

I can't pull the card out yet because of warranty - I am contacting my vendor again today.