Discussion Locked

Can't map to server - server not found?

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have 3 new IBM M-Pro workstations that will not allow me to map a drive to an NT server. These machines are not in a Domain.

when I map to \\IP\share, it comes back "Server can not be found"

All the other Win2000 machines I have (notebooks,desktops) will map to the NT server no problem.

All the Network connection, IP, Client etc settings all appear to be the same. There must be a setting somewhere I am missing or possibly a parameter for a component that causes it to time out before connecting to the server?

12 replies

by garv

The actual message I get is: "The network path "\\168.65.228.65\home" could not be found.

Using the same user account, same network jack etc. Something on these 3 machines (the only 3 M-pros I have) is different from all the other machines and I can't find it.

by qb

I beilive you should carefully verify your IP settings. Any typos or oversites in the Ip settings and you're SOL. Also if you are not running DNS or WINS the you need to make sure that you install NETBUEI along with TCP/IP. Start with these.

by garv

I've already checked all the obvious IP, DNS and Netbuei settings. We don't use Wins. The mapping is done using Tools-Map a drive and using "\\168.65.228.65\home" to a standalone NT server. No domain in the scenario either.

by stillatit

There are no timeout settings you should be concerned with.

Here is a quick checklist:

IP addresses are unique
IP addresses are correct for your network segment
Masks are correct
Default router correct if you are not on the same segment as the server
Client for Microsoft installed
If Netbeui installed, NO scope value or identical value to server

You do not care about DNS or WINS at this point, since you are using an IP address.

These sound stupid, but...

Net cable from the wall to stations the same as to a working station (or did you pick up an X cable by mistake?)

Do you get a connection light on the card?

If the card has multiple ports (TP + BNC), is the card set for the port you are using?(some have to be set via software or switches)

If you have a spare hub around, if you plug in the station, do you get a connect light?

If you are plugging into a hub for testing, does the hub have power (Had a user do this last week...) and is the network cable in the uplink port (or the uplink switch set)?

Tests for IP:

Can each station ping 127.0.0.1?
Can the stations ping each other?
Can each station ping the server?
Can the server ping each station?

Good luck.

by izz

Well when u connect to a share, the Domain controller checks your request to see if u have enough permission ot a share, or even if ur account exists in the domain. And as u said they are not joinning a domain, then how will they connect to a share.The main difference between a workgroup and a domain is the security, which in the workgroup is managed on a workstation basis whereas in a domain it is all controlled by the server.

Hope this helps.

by garv

There is no domain in this scenario. The Win2000 Pro workstations are mearly trying to connect to a share on a standalone NT server. All other workstations (NT and 2000) in the environment can connect. It is only 3 of the new ones that will notand I can't find the difference in machine settigs anywhere to explain it.

by qb

Did you add a computer account on the NT server for each of your new computers?

by garv

Like I've said, there is no domain in this scenario. Only a standalone NT server - so computer accounts for workstations connecting to a share are not needed - right? Or am I missing the big picture? But, non of the other 100 or so Win2000 PCs have computer accounts on the NT server and they can connect to the share no problem.

This discussion is closed to new replies.