Computers dont see each other!?

[s3ntry]

I set up a small home network using a Linksys BEFSR41 Router with 4 port Switch. I have 3 computers networked, sharing one ADSL access. All 3 computers are running Windows ME and the router is running the latest firmware.

I use NetBEUI as my LAN protocol and TCP/IP only for the internet. The network settings are as follows:

- All computers have different names and are on the same workgroup.

- On each computer the NIC is bound to TCP/IP and NetBEUI.

- NetBEUI is bound to "Client for Microsoft Networks" and "File and printer sharing for Microsoft Networks".

- TCP/IP isnt bound to anything.

- 2 of the computers are getting their LAN IP addresses from the router's DHCP server, while a third one has a fixed LAN IP address and is on the router's DMZ.

Before explaining the problem let me tell you that I can access the internet from all 3 computers with no problems and i can run server software on the DMZed computer. I also have one printer shared on one of the computers and i can print to it from any of the 3 with no problems. And I can access the shared folders on any computer and transfer files between them with no problems either.

In fact everything would be perfect if it wasnt for one little problem... the computers dont "see" each other on the network!! When i open "My Network Places" it gives me a blank screen as if no network existed and to access the shared folders i have to type their full network address on the explorer address bar. That's the only way to access them since i cant normally navigate to them because nothing shows up on explorer! After typing the network address of a shared folder i can access it normaly as if it was local.

Can anyone tell me why this is happening? How can i make the computers see each other and browse the network normally?

Thanks in advance

[cyberskye]

Do you have the accounts (usernames) you use on all machines - ie - user "John" existing on all machines? I believe that is required to browse...

Alternatively, you could probably map a network drive to a specific share and set it to 'reconnect at login', but that would be fairly messy if there are a lot of shares.

You may not want to have a common account on the DMZ host. Personally, once I put a machine in a DMZ, I assume that it is comprimised and will not let it have access to the rest of my LAN without reformatting. Then again, I am paranoid :p

Luck,

Skye

[s3ntry]

I dont have all the same users on all the machines, no... but i dont think thats a requirement if your access control is on share-level (like mine is) instead of user-level.

I already thought about the mapping solution but it would be really messy, i'd rather just be able to browse the network normally, like i should be able to.

As for the DMZ computer, i need to do a lot of video conferencing and i can only do that on the DMZ, so i keep that one permanently there since i have the webcam connected to it. That's why i run a software firewall on that computer :)

[twwabw]

I've seen this happen before on 98 peer-to-peer lans, although not in a long time. Haven't had to work on a 100% ME lan ever, but I can tell you there are lots of "issues" networking with ME- more than 9.x ever thought of! Anyway, 9.x / ME networking can be a little flaky sometimes, and you have to experiment if you have problems.

In order to browse, the network needs a master browser. In a domain environment, this is easy- the domain master browser is always the PDC. Then, depending on the number of network clients, and their order of login, backup browsers are chosen. These all maintain the network browse list, allowing you to view the list of available resources. If an NT server, workstation, 2000, or XP client are found, they become the backup browser in order of preference.

MS networks made up for their lousy browsing scheme in other ways too, like the dreaded WINS server :mad: . This provides name resolution. This of course relies heavily on netbios to function, which is one of the things you're trying to eliminate by unbinding CFMN and F&PS from TCP/IP.

None of these may be an exact explanation for your problem, and if you cruise the MSKB for answers, you'll find lots of them, most ending with "Microsoft has confirmed this to be a problem with ......"- great answer, huh? And, I truly think you've compounded the issue by having an all ME network. ME has notoriously been one of the biggest networking headaches for admins since it came out. It just plain sucks. Sorry about that, but it's true..... it's so bad, and causes so much grief, I have flat refused to work on one at client sites. Install 98, NT, or 2000, or you're on your own! I have spent countless hours trying to resolve ME login problems; browsing; RAS problems; VPN; etc., that I've washed my hands of it.

But, here's what I'd try first:

- Uninstall networking protocols on all PC's, the re-install them. Set it up again the exact way you had it before. Problem solved? Great.

- you can cure this instantly by going to fixed IP's on all clients, and entering client info. into the HOSTS file. You'll find one windows\hosts.sam . open this file in notepad, and enter ip's and names in the same way the localhost is shown. Choose save as, select "all files" not text, and enter hosts with a period after it. This will provide name resolution for the clients.

- Unfortunately, the other sure-fire way to cure this is to (gulp) install TCP/IP, and enable net bios over tcp/ip. Guaranteed your browsing problems are over. But obviously, you know this is not what you should do- you are now wide open.

- Last option (my favorite :D )- ditch ME and install Windows 2000 on all clients. Problems solved :nod:

Post back with any updates!

Tim

[s3ntry]

Thanks for the suggestions, i'll try some of those. I had already tried the move everything to TCP/IP using NetBIOS one, and verified it did work, but i went back to NetBEUI for obvious reasons, i'd rather have to type the addresses everytime than have my network wide open for everyone to see!

As for upgrading the OS'es, i know WinME isnt the best thing out there, but it has worked okay for me and does all i needed it to do, it's fairly stable on all my systems, its very compatible with all my hardware and software and it was way cheaper than Win2k would be :) Maybe i'll look into upgrading to XP Home in a near future, but i read that XP doesnt even come with NetBEUI anymore, it uses TCP/IP for everything and then relies on a lame integrated firewall to cover up for the holes! Not very appealing...

[cyberskye]

You can add Netbeui to XP - somes on the CDROM - they just don't offer it by default anymore.

Networking with a non-networked os will always be problematic. My girlfriend has ME and my suggestion got her to be able to browse my W2K machine and my SMB shares.

I would be very careful about running servers on ME if you are really concerned about security. My girlfriend's brother works for microsoft - poor bastard - and even he admits that ME is the worst OS they have ever put out. XP Home has had some compatibility problems - I have read more than a few posts at speedguide where folks have backed out to 98. Alas, support for 98 is just about over.

At least for the server, I would throw out the bucks for W2K.

Have fun,

Skye