SG Broadband Community

First Question:

Not too long ago, the computers I have stopped showing up on the network neighborhood.

Here's the setup on each computer:

Different computer names
o Same workgroup
o NetBEUI LAN
o TCP/IP WAN
o TCP/IP binded to everything BUT MSNetworking Client and Filesharing
o NetBEUI binded to everything BUT dial-up adapters
o WindowsME (puke) on each machine

What's strange however, I can still explore to \\Computername\Sharename and continue as normal.

I've tried deleting all of my adapters, protocols, etc. It seems that no matter what I do I still have the same problem (computers don't show in Network Neighborhood).

Any suggestions?

-----

Second question:

When I share files from one computer to another, all is fine. All computers have a RealTek 8139 card in it BUT the one I have problems with - which is a 3Com (don't remember model #).

The problem with the 3Com computer is, after I've browsed with Explorer through the different folders, transferred files, etc, browsing gets EXTREMELY lagged! When it finally responds, the file transfer goes at a normal rate. Then I start to go from folder to folder again, and it gets lagged AGAIN.

Now transferring files from one RealTek 8139 to the other has no problems at all.

I've checked to make sure full duplex is enabled on all cards.

Any solutions?

Ok to your first question. Do you have a firewall installed on either of the computers. That could be blocking you from seeing the computer on the LAN. It could be hiding it for security purposes.

If you are running ZoneAlarm than you may want to turn network security down to medium. If you are running a different firewall you may want to investigate the settings to see if that would have an effect on it.

I had that happen to me. Zone alarm was the problem too.

No I don't have any firewalls up. All the security I really need was making sure that TCP/IP and the MS Networking Client/File Sharing weren't binded.

What else do you think it could be?

Welcome to Windows ME. You've seen just one of the trillion reasons we network engineers hate it.

I've yet to find what causes this in ME. I can setup Win9X/NT networks in my sleep, and have name resolution occur instantly. But for some reason, some machines with ME take a long long time to resolve. I'm talking days and days and days.

Just a couple of weeks ago, I setup a small mixed home network for a client, on a router and cable modem. It had a 95 machine, 2 98 machines, and 2 ME machines. I did my usual setup, had NetBEUI bound, and TCP/IP loaded, but not bound to networking. All but one of the ME machines had instant browsing and name resolution on the LAN. The newer ME machine, brand new 1.0gHz 512 meg video editing rig, couldn't populate the neighborhood, but you could do a search for any computer and bring it up that way, or via share name.

Ran all the updates, rebuilt the network components from scratch, to no avail.

I ended up making a shortcut on the desktop to the other computers shared drives, so it was easy to get to them quickly that way.

A week later....she said the computers finally appeared in the network.

Yet the other ME machine instantly saw them, I've setup other networks where I've had similar experiences, some ME machines instantly work, others take a long long time.

Glad ME will end it's production soon, it will barely have made it over 1 year. When did it come out, end of July, early August last year? And it's being replaced this fall thank god.

You can also click right on network properties and map the computers name and add it to my computer by dragging it in mycomputer so is doesn't have to be on the desk top. This one of the reason I went back to to win 98. Also try enableing Quick connect in the properties for ckient for MICROSOFT NETWORK. This may help you out to. Good Luck! Also I notice with many of the other flaws in Me if possible run autosenseing on your cards not full duplex. It seem to Bog down files transfers. Till they make it better I will stick with my version of 98 . It run great never gives me a proublem.


[ 05-14-2001: Message edited by: Storm90 ]