I tried connecting a Win98 pc to a Win2000 server the other day and with tcp/ip installed I thought I should be able to browse the network, but it wasn't until I installed NetBeui that I was able to see the other pc's in Network Neighbourhood. Is that correct?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
A few questions:
Can you ping the win2K server from the PC by IP address?
Can you ping it by name?
Are you trying to ping other machines on the network by name and/or address or do you want to see a list of names in the computers near me under network neighbourhood icon?
If you put the network clients names in the lmhosts file for W98 this should help with name resolution - if you are using DNS or Wins then it should already be working.
N
Have you enabled NetBIOS over TCP/IP?
http://support.microsoft.c
NacMacFeegle:
1. Yes I could ping the win2k server from the PC using IP without NetBeui
2. I will have to remove NetBeui and try pinging by name - will be in the next couple of days hopefully (neighbours PC)
3. I want to see a list of names in the computers near me under network neighbourhood icon?
4. I'm using Winroute on the server. I never know the difference between the Hosts and LMHosts files?
FishMonger: Have I enabled NetBIOS over TCP/IP? - I didn't specifically, I will have to check the setting.
Will using NetBeui slow the network down?
Seems like you are operating in a Workgroup environment. And I'm afraid that you have to install NetBeui protocol on your Win98 in a Workgroup environment.
Win98 uses NetBeui to resolve computer host names wheras Win2000 can use the NetBios over TCP/IP to do that (it should be ON by default). So without NetBeui installed, Win98 cannot retrieve the browser list from the master browser (which might be the Win2000 machine), thus unable to view the internal network computers.
And NetBeui will not slow the system down till human can feel the difference.
daveteh,
Sorry but you're in error, Win98 does have the ability to use NetBios over TCP and doesn't need NetBEUI in-order to retrieve the browser list. In fact, the system that I'm using right now is Win98 in a workgroup environment with W2K, Solaris, and Linux, and I removed and haven't needed NetBEUI for that last 3 years. On another side issue, the computers receive their browser list from the back-up browser which receives its list from the master browser and the master browser is the computer with the latest version of the browser service which may or may not be the W2K machine. Other factors are the version of OS, which computer has been "on-line" the longest, and whether it's a workgroup or a domain [in a domain, the domain controller is always the mater browser or more correctly, it's the domain master browser].
nickwoolley,
NetBEUI has less overhead than TCP so it is a "faster" protocol, and it shouldn't slow down the network but it is a "chatty" protocol. However, since it's not as robust and doesn't have the error checking that TCP has, it can slow down the network to a crawl if there are allot of CRC errors and retransmissions of the data i.e., broadcast storms. There are several other factors which make it a less desirable protocol which I won't go into but even Microsoft is trying to move away from using it. In case you haven't noticed, they didn't include it in XP and I don't think it's included in any other of their server OS's since W2K.
I've never used it but I have a feeling that your problem is stemming from Winroute. Have you checked its configuration to make sure it's not blocking the connection?
I forgot to address your confussion between the hosts and LMhosts files. Your computer can/will use several means to resolve the names (Wins, DNS, hosts file, LMhosts file, and broadcasts). I don't recall the precise order in which it uses those means but broadcasts will be the last method used. The hosts file is a mapping of the IP addresses to host names and the LMhosts file is a mapping of the IP addresses to NetBios computer names. Most of the time, the host name is the same as the NetBios name, but it doesn't have to be. Also, you can have only one NetBios name for the computer, but you can have multiple host names for it.
Nickwooley
have you looked at MS KB article 192534? This discusses troubleshooting Win9x network connections. I must say I'd never heard that you need netbeui to resolve the browse list for winfows 98 in a workgroup configuration and would be interested in seeing a reference for this. I'm sorry I don't know anything about winroute so this could be your problem. Essentially on reboot the Server should hold an election to see who the browse master for the network is (this should show up in the event logs). When a in9x/NT box tries to browse the network my understanding is that it sends a broadcast to find the browse master for the network. The browse master (or backup browse master) then tells them who is on the network. If you look at MS documents it all gets horribly complicated quite quickly though. As I said I would look at winroute as one likely cause.
N
Business Accounts
Answer for Membership
by: jvuzPosted on 2003-09-22 at 05:27:43ID: 9405189
No, normally it should work with TCP/IP