 |
This
is a summary of some network problems we have experienced
in the past, and fixes we have used to resolved these issues.
Click on the links below: |
During
autoregistration, we get an error such as, "SGL failed....."
or "failed to register with.........Network Manager
The connection has failed
The computer does not recognize
the presence of the card when you first insert it. It
just boots right to Windows.
The computer is very old. The
card installs, but the device manager tells you there is a Device
Failure in the General Tab of the adapter’s properties.
The computer is a new Compaq Presario
or HP Pavilion. The card seems to be installed.
The settings are all correct. The IP address continues
to be 169 or 0.0.0.0
The installation completes successfully.
When you look in the device manager, you see that there is more
than one network adapter present.
The computer is an older
Compaq Presario. When I insert the card, and power the
machine up, the computer tries to boot from the network.
Then, all I get is a blank screen.
The network card seems
installed, but I cannot get IP addresses other than 169 or 0.0.0.0.
When I look in the device manager, it is filled with all kids
of protocols and devices.
The card is installed fine, but
it is getting a strange, non-SUCO IP address.
The computer runs Windows 95.
There is no connections. When I go to WINIPCFG, I get
a “Fatal IP error”. Re-installing TCP/IP does not solve
the problem.
Situations requiring professional network
intervention.
During
autoregistration, we get an error such as, "SQL failed....."
or "failed to register with.........Network Manager
top
Any
error containing the text, “SQL Failed” or “Failed to register
with……..Network Manager” needs to be brought to our attention.
We’ll contact staff responsible for the scripts that run the
autoregistration page to try and fix the problem. Return
to the individual later and try to help them autoregister again.
Initial install of NIC does not result in a connection:
Resulting IP address is 169…. Or 0.0.0.0
1.
Check the adapter on the computer. Do you see lights on
the adapter?
- If
yes, there is a viable connection, and the problem is somewhere
else.
- If no, check the cable. Is the cable plugged into
the RED port? Is the cable well inserted into the adapter
in the computer?
- Does the cable look like a very cheap brand? Test one
of our cables with the computer. We have seen instances
where switching the cable fixed the problem.
2.
Check for Device
Conflicts
- Go to the Device Manager. Double click
on Network Adapters, and double click on the adapter
you installed. There should be a yellow exclamation point
through it.
- If the General tab of the adapter properties
sheet indicates a device conflict (This device is causing a
conflict…..), go to the Resources tab.
- The Resources tab will indicate which device
is causing the conflict.
- You can change two settings: IRQ and I/O
address. Highlight the setting which is idicated to
be causing the problem.
- If both IRQ and I/O settings are indicated, start
with the IRQ, and move on to the I/O later.
- Click on “Change Settings”.
If the computer does not tell you that the setting cannot be
changed, move through the numbers with the little arrows, until
you come to a number w/o a device associated with it.
Click ok. Do the same thing for I/O address if
necessary.
This is a technical situation
that may not be easy to fix.
3.
There is no device conflict. Re-install the existing adapter.
- Go to the Device Manager. Highlight the
network adapter and click Remove. Accept the confirmation
prompt.
- If the computer asks you to restart, CLICK NO.
Shut the computer down yourself.
- The clean way to re-install is to physically remove
the adapter, and restart the computer with no network at all.
Then, shut the computer down, and attempt the installation again.
- Another thing you can do is to place the adapter into
a different slot. This will frequently result in the system
detecting the card.
4.
Re-installation still does not solve the problem.
- Obtain a known good Ethernet card, with its driver,
and install it as a test. If this card works, the student
has a bad card.
- If the known good card doesn’t work, it’s time to suspect
the port. If the computer’s cable can reach, place the
end of it into the roommate’s port.
- If the problem is solved, there is a port or server
issue (if there are lights, it is a server issue).
- Call professional staff who will bring a port tester
and laptop to the room to test the port. If the laptop
cannot log in, there is a problem with the server.
- Time for professional network intervention. Log
the call as unresolved and referred to Raphael. Reschedule
with the student.
The computer
does not recognize the presence of the card when you first insert
it. It just boots right to Windows
top
- Shut the computer
down, and remove the card from its current slot. Place
it in a different slot, and attempt to install.
- We have seen numerous instances where simply changing
the slot will get the computer to recognize the card.
- If changing the slot doesn’t work, test a known good
card with its driver.
- Attempt a manual installation of the card through the
Control Panel/Add New Hardware.
The computer
is very old. The card installs, but the device manager
tells you there is a Device Failure in the General Tab of the
adapter’s properties
top
- We have seen
some very old machines that give this error, because TCP/IP
has not been installed with the card.
- Go to the Network Neighborhood Properties.
Click Add. Click Protocol.
- When the Protocol window pops up, choose Microsoft
on the left, and TCP/IP on the right.
- After this has finished, double click on TCP/IP
for the network adapter in the Network Neighborhood Properties.
Make sure all settings are correct. Restart the computer.
The computer is
a new Compaq Presario or HP Pavilion. The card seems to
be installed. The settings are all correct. The
IP address continues to be 169 or 0.0.0.0
top
- The following situation has been observed in the above
listed machines: A competing network adapter is installed.
It is called a Lucent V90 DSL/LAN Modem.
- Disabling this device in the device manager has successfully
restored the connection.
- Go to the Device Manager. Go to Network Adapters.
Double click the Lucent Device.
- In the Lucent properties, check “Disable in this
hardware profile”, and uncheck “Exists in all hardware profiles”.
This will disable the Lucent device.
The installation
completes successfully. When you look in the device manager,
you see that there is more than one network adapter present
top
- New computers frequently come with drivers installed
for network adapters that aren’t in the machine.
- Removing these adapters in the Device Manager, and in
the Network Neighborhood properties, should solve the problem.
- Before you do that, ensure that the card you installed
is the ONLY adapter in the computer.
- Look at the back of the computer, and make sure that
there is no network adapter integrated into the motherboard.
- This has been an issue with some older Compaq Presario
machines.
The
computer is an older Compaq Presario. When I insert the
card, and power the machine up, I see that the computer tries
to boot from the network. Then, all I get is a blank screen.
top
- This is happening because you are trying to install
a card into a machine that already has a network adapter in
it.
- Look at the back of the machine, up around where the
keyboard and mouse connectors are.
- If you see a network adapter there, remove the card
you tried to install, and simply configure the computer for
the network.
The
network card seems installed, but I cannot get IP addresses
other than 169 or 0.0.0.0. When I look in the device manager,
it is filled with all kids of protocols and devices.
top
The
following things should be removed from the Network Properties
if they are present:
- Any reference to NetBEUI (Highlight, click remove).
- Any reference to IPX/SPX (Highlight, click remove).
- Any reference to Banyan Vines Protocol (Highlight, click
remove).
- Any reference to Client for Netware Networks (Highlight,
click remove).
Remove any reference to VPN. VPN is a Microsoft
encryption standard that allows for secure transfer of data
over the internet. It stands for Virtual Private Networking.
You uninstall it in the Control Panel:
- In the Control Panel, go to Add/Remove Programs.
Go to the Windows Setup tab.
- Scroll down to Communications and double click.
- Look for Virtual Private Networking. Uncheck the
box next to it. Click Apply. Click OK.
- When you reboot the computer, make sure to go
into the Network Neighborhood Properties, and the device Manager,
and manually remove any remaining reference to VPN.
The card
is installed fine, but it is getting a strange, non-SUCO IP
address
top
-
The computer has been hard coded for that IP address.
- You can tell this if you go to WINIPCFG, choose
the network adapter, and see that the Release/renew buttons
are grayed out.
- Go to Network Neighborhood
properties, and set the machine to DHCP. Make sure all
other network settings are appropriate, and restart the computer.
The
computer runs Windows 95. There is no connections.
When I go to WINIPCFG, I get a “Fatal IP error”. Re-installing
TCP/IP does not solve the problem
top
We
have encountered Win 95 computers that successfully respond
to the following fix:
- Restart the computer in MSDOS mode. You will be
at c:\windows\system prompt.
- Type cd ws2bakup. You will now be at the c:\windows\system\ws2bakup
prompt.
- Type. Ws2bakup.bat and hit Enter. The entire Winsock
software, which controls the Win 95 connection will be re-installed.
- When the process is complete, restart the computer and
test the connection.
- This fix is only valid for Windows 95.
Situations Requiring
Professional Network Intervention:
top
- After autoregistration, the computer gets a 169,
or 0.0.0.0 and will not release it. The connection was
fine before, because the computer was able to get the autoreg
page.
- After autoregistration, the computer will not release
its 192 IP address.
- There are no lights on the adapter, and a port tester
reveals a poor connection.
- There are lights on the adapter, but a known good test
laptop cannot log in.
- There are “SQL Failed” or Failed to Register With Network
Manager” errors after autoregistration.
top
