General discussion

Locked

Problem with NT 4.0 Server

By mrdbcooper ·
The system is NT 4.0 Server with SBS 4.5

Have ten machines running on the server and
am hooking up a new unit.
Upon hooking up the new unit and then trying
to access a shortcut that refers to a file
on a share drive I get an error dialog message
of The Drive or Network Coonection that the
shortcut exists on is unavailable.

I have enough licenses on SBS 4.5 to add the
new unit. I have checked the regestry of the
server for any pipe problems that might be
locking the new unit out.And I have checked
the registry of the new unit. Everything is
fine on those levels.

Let me know what the work around is because the
KB at MS is of no use and outside of using
voodoo sacrifice rituals I am at my wits end.
I need to get this unit up and running soon.

Thanks

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Problem with NT 4.0 Server

by Joseph Moore In reply to Problem with NT 4.0 Serve ...

Does the shortcut reference a mapped drive, or a full UNC path? If it uses a mapped drive, make sure the new system has that drive mapping. Set up the drive mapping either with a logon script or right-click on Network Neighborhood -> Map Network Drive.
Now, if the shortcut points to a UNC path (\\SERVERNAME\SHAREDFOLDER\filename.ext) then make sure this new machine can PING the SERVERNAME the shortcut is pointing to. Open a DOS Command Prompt and type in PING followed by the machinename. If the machinename does not resolve correctly (if you get a Host Not Found error), then make sure the new system has the correct WINS server information for your network, if you run WINS. If you do not run WINS, then you can add the remote machinename andits IP address in the LMHOSTS file on this new machine.
Here is a TEchnet article on the LMHOSTS file usage, article Q180094:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q180094
(please remove any spaces)


If neither of these things seem to work, then make sure the new system has the correct IP address settings, including the right IP segment, subnet mask and default gateway. See if this machine can PING other machines on your network by either machinename or IP address.hope this helps

Collapse -

Problem with NT 4.0 Server

by mrdbcooper In reply to Problem with NT 4.0 Serve ...

Poster rated this answer

Collapse -

Problem with NT 4.0 Server

by VinnyD In reply to Problem with NT 4.0 Serve ...

What is the OS of the new unit? Was it joined to the Domain?

What service packs are installed on the server?

If the machine is windows 2000 or XP Pro you may need to load service pack 6a for nt 4.0 on the server to get the security fixes.

Collapse -

Problem with NT 4.0 Server

by mrdbcooper In reply to Problem with NT 4.0 Serve ...

Poster rated this answer

Collapse -

Problem with NT 4.0 Server

by mrdbcooper In reply to Problem with NT 4.0 Serve ...

For those whom need the info its NT 4.0 Server
with SP5 serving NT 4.0 Workstations with SP5.

Also have pinged (as suggested) the box with
the problem to the server, print server and
other machines and it does ping but with a
delay. Packets are sent out and received by
the machines but it takes a while for the
results to return from the pinging. Perhaps
there is a clue there?

Collapse -

Problem with NT 4.0 Server

by Rabbit_Runner In reply to Problem with NT 4.0 Serve ...

I am not certain if this will help. Normally default shares are limited to 10. When you create a share, it is set to 10. you may need to increase the number of allowable connections.

Collapse -

Problem with NT 4.0 Server

by mrdbcooper In reply to Problem with NT 4.0 Serve ...

Poster rated this answer

Collapse -

Problem with NT 4.0 Server

by mrdbcooper In reply to Problem with NT 4.0 Serve ...

To answer the third question I have the
file server access to allow maximum users.

Collapse -

Problem with NT 4.0 Server

by cavedweller In reply to Problem with NT 4.0 Serve ...

I believe that SBS is limited to 10 users no matter what. You will need to convert to NT-4 server (end of life) or one of the newer versions if you want to expand.

Collapse -

Problem with NT 4.0 Server

by mrdbcooper In reply to Problem with NT 4.0 Serve ...

Poster rated this answer

Back to Windows Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Operating Systems Forums