"This device does not exist on the network" If I see that one more time...

[Zorn]

I'm upgrading a four client, one server network for a small lawfirm. The system they were using until this weekend was Netware based, circa 1991. I upgraded two of their client stations two weeks ago, the other two client stations are reasonably new. Three clients run Windows98SE, one client runs Win2k.

This weekend, I transfered the files from the Netware server (all 833 megabytes..LOL) to the new server and plugged the new server into the network...given that there are only four clients and cost was an issue, the server is running Win2k PRO SP2. I added the four users to the Win2k user database and told the client computers to stop using netware login and user level access and start using MS client login and share level access (internal network security is not a primary focus and the clients will share no files).

The result was the flakiest network I have ever countered. The Win2k client happily connected. The Win98SE clients have been an exercise in frustration. Occassionaly, I would get one client to see the server, but then it would lose sight of the server during the same login session and would invariably lose it if I rebooted. Long story made short, after several driver reinstallations I got all four clients to see each other on the network and I got two of the three Win98SE clients to see and access the server. The third Win98SE client sees the server on the network, but when you try to access the server, I receive the following message (which I now loathe):

"This device does not exist on the network"

Now, clearly, the device does exist, because I can see it and it's always there, its just not accessible. One of the other Win98SE clients will also give this message, but it seems to resolve itself after a minute or two after reboot (which is weird as hell). Meanwhile, all the clients can happily see and access each other...naturally, the problem lies exclusively with accessing the server.

Right now I'm using TCP/IP protocol and the network is running through a linksys 8 port switch/router (I've tried a regular 8 port switch as well). I have also tried entering other usernames at the station that refuses to connect, still no connection.

I initially thought my problems were based on the residue left behind by the Netware client login configuration. But, I've reinstalled the network drivers at least five times. Ugg! I'm stumped. Anyone else experience this? Any help would be greatly appreciated as I'm slowly losing my mind.

 

[Saltin]

How are you resolving computer names and services on this network?

 

[Zorn]

Hmmmmm....now, that I think about, that's a very good question. I was using DHCP from the router and originally configured the network to use NetBeui. That configuration didn't work at the time because there was an issue with the Network driver on the server -- i.e., I had to reinstall the drivers, which magically caused Win2k to see the network and become accessible to serveral computers. But, by that time I had wiped and reinstalled all network drivers at each workstation. Netbeui is not installed on the network anymore (If I had to guess anyway, I'm not at the site today).

Being an admitted neophyte when it comes to anything more than peer-to-peer, could the fact that all computers are configured for DHCP and the router is acting as a DHCP server, cause this to happen?

 

[Saltin]

Well, it's not a good idea to use DHCP unless you have implemented dynamic DNS or WINS. It doesnt sound like you have either.
Try this and see if your situation improves.

Each computer recieves a static IP and TCP/IP info.
On each computer, search for the LMHOSTS file, and enter a record for each computer. It will go something like

<computername> <IPADDRESS>

There are examples of the syntax in the file, its not hard to do.
When you are finished, each computer should have a listing of every computer on the network (including itself) in it's LMHOSTS file.

Also, enable Netbios over TCP/IP on the 2k box (if it isnt already). You can find this in the TCP/IP properties, advanced button.

Remember, the computers need to know where and who each other are in order to have complete connectivity. The LMHOSTS file mappings will allow this, and turning off DHCP will mean the addresses dont change, which can make for a bad situation in your case.

 

[Zorn]

Thanks for the advice. I'll try assigning ip addresses and adding records. Should make for a much more sound network regardless. I guess I'll have to disable DHCP assignment in the router and reconfigure it a bit as well.

While we're talking about servers and clients, as I indicated, I've never configured a file server-workstation network (I have setup webservers,and plenty of simple peer-to-peer, but not strictly files servers) and I'm using Win2k Pro, which obviously, doesn't have handy file server configuration wizards that Server has. So, what I did was create restricted folders based on user types and preferences on the Win2k box and then map network drives from the individual stations. Is there a more elegant way of configuring the clients and server than what I'm doing? Anything else I should know about configuring Win2k Pro to acts a file server?

 

[Saltin]

Mapping drives sounds like a good solution to me.
The only caveat I can think of regarding 2k Pro as a File Server, is that it will only handle 10 concurrent connections. It doesnt sound like you have more than 10 boxes, so you will be ok.
It is something to keep in mind if the network is expected to grow, however.

 

[Zorn]

I just got a call from the law firm, seems all three of the Win98 computers can't access the server anymore, though one could for about an hour and then it started receiving the same message as the other two: "This Device does not exist on the network."

Meanwhile, the Win2k Pro "server" and the Win2k Pro client can access each other fine and all of the Win98 comptuers can access each other.<Sigh> I'm getting over there tomorrow, hopefully, creating an LHHOSTs file for each system will resolve this problem.

Good thing I put a backup copy of the server on a Win98 client which they can use till I get there.

 

[spidey07]

looks like you should have stuck to a more network friendly OS. Like netware.

oh man, I couldn't resist that one. sorry.

 

[Zorn]

LOL...although they were connecting to a 486 based server with a 1.5 gig harddrive that took over an hour to transfer 833 megabytes of information over the network, they were indeed CONNECTING, hassle-free, everytime....and then I went and threw Microsoft into the mix. :Q