Printable View
Windows Me cannot log on to the NT domain and I also get this message "Unable to Browse Network
Windows is unable to gain access to the network. This may be for a number of reasons. For more information, click Help."
I would like to get connected to the network,
The funny thing however is I get a lease from the server for this workstation. How is it I can get a DHCP lease and not be on the network? <IMG SRC="smilies/eek.gif" border="0">
Can I firstly say that ME is cack on networking.
Now to the problem....What protocols have you got installed on the client?
To make sure of a reliable (Not efficent) connection install the same protocols as the server.
Next, make sure that the domain name is set correctly, net try and use a free IP address and the same subnet mask as the server.
If all else fails, let me know, but I need to know how you have set the network up on your client. Have you tried copying another clients setting?
...are you logging into an nt account that is enabled?
i presume me is roughly the same as 98, because in 98 you must "log into" a specific a/c, which can also be the "guest" a/c.,
condor may be able to give a fuller answer!!!!! <IMG SRC="smilies/confused.gif" border="0"> <IMG SRC="smilies/tongue.gif" border="0">
you ARE physically on the network...Quote:
Originally posted by Coxswain:
<STRONG>The funny thing however is I get a lease from the server for this workstation. How is it I can get a DHCP lease and not be on the network? <IMG SRC="smilies/eek.gif" border="0"></STRONG>
you get an IP-adress from a DHCP-server on that "Server" to be able to logically connect to the network - you definetly NEED this IP to be verified or even not-verified as without IP you can't even connect to the verifying mechanism on the server
Now that you are "not on the network" only means, that your account/machine/ip-adress/OS/whatever isn't allowed to connect to that particular DOMAIN you wanted to connect - nothing more or less.
Try to setup an account/password on the server and login with that appropriate account on the non-NT-machines
Make sure NetBEUI and IPX/SPX Protocols are installed, I think they are necessary for networks, but maybe that is just my network. Well give it a shot anyway.
Make sure NetBEUI and IPX/SPX Protocols are installed, I think they are necessary for networks, but maybe that is just my network. Well give it a shot anyway.
no... they are both not necessary for most part... only some applications need these to connect, but the main network could (and should) work without them... so leave'em uninstalled if you don't need'em!Quote:
Originally posted by em-clown:
<STRONG>Make sure NetBEUI and IPX/SPX Protocols are installed, I think they are necessary for networks, but maybe that is just my network. Well give it a shot anyway.</STRONG>
I'm going to have to disagree with you here. This is correct for an efficent connection, but to make sure the connection is working, first you must install Netbui and IPX to obtain the connection.Quote:
Originally posted by ?¿?:
<STRONG>
no... they are both not necessary for most part... only some applications need these to connect, but the main network could (and should) work without them... so leave'em uninstalled if you don't need'em!</STRONG>
By the way, if the server goes down and you want this computer to use another computers files or printer, it will work, not if you only have TCP/IP installed.
Sorry to argue.
I'd like to hear that from different people - as I'm sure to be right ... and I think this NetBEUI-thing is spooking around in many networks - without beeing necessary.
NetBEUI is indeed much simpler than tcp/ip to configure... but if you know the ip-stuff, ip-packets will reach the destination likewise (and they do!). In addition to that TCP/IP is routable... NetBEUI not what mkes NetBEUI senseless for more than a home-net...
IPX is the better choice (it is routable) but why should people use an additional protocol (=overhead)? TCP/IP has to be run to access Internet (and that's what most folks want) and in my opinion there's no need to use more than this (or the special app wants it... that's another thing)...
BTW: TCP/IP really isn't so efficient... but it's spread out like MicroSoft... so what? we couldn't ignore that... or create a second Internet!
First, I'd like to disagree to the last post (no offense) and say that TCP-IP is a very valuable protocol that would make us very lost in many instances if we did not have it. I would, to make sure you are getting the correct connections, go to your ME machine and set a permanent IP address on it. Then go to the command prompt (run cmd) and ping the IP number of your ME machine to see if there is any connectivity between the two.
I agree with last post, set a static IP and ping your ME Machine. Getting back to the basics, has anyone mentioned checking to see if you've named the Workgroup correctly. You can also set up one of the other machines to a static IP w/ different w/g, set the ME up with the next IP and same w/g, and you should be able to see the two machines in n/w places by themselves. That'll eliminate everything but configing to the server. On the NetBeui topic, some programs do rely on it to share the database. From what I've seen, Legacy based dbases seem to work better woth it running.
Explanation of the two protocols:
TCP/IP - A numbering system that gives the computer a number to comunicate with other computers on the network. Meaning that it gives the computer a name to communicate with other systems on the network. If the server is having problems with DHCP then the computer cannot obtain a user name. If it has a specific address matching the servers first three strings and matching the subnet mask and the network goes down, the workstation can communicate with other workstations if the server goes down (Provding other clients are set-up the same way).
This is a good way to set-up the network if it is small and managable. If you are setting up a large network and have no way of keeping records of the address's I would suggest seting up the DHCP.
NetBEUI - A protocol that assigns a name to the computer that has been specified on the machine. Depending on how you want to set the machines up, it is a good option.
If you are using RAS through the server I recommend removing this protocol as this causes a speed issue. Over a 10/100 network this protocol is good.
Coxswain......How is your network set-up? How is the client set-up?
Can you please let us know.
Think that topic will expand to a general discussion about protocols... i'm sorry about that but I can't let some things be open...
It's no offense, as i'm pleased to discuss... and I never said TCP/IP isn't valuable... but it's not that efficient (overhead, adressrange ...) so you're right.Quote:
Originally posted by aplustech:
<STRONG>First, I'd like to disagree to the last post (no offense) and say that TCP-IP is a very valuable protocol that would make us very lost in many instances if we did not have it.</STRONG>
TheBear, I hope you don't feel attacked ... I can't see why you want to defend the use of NetBEUI... it's a very proprietary protocol with disadvantages (Scooter: thanks for mentioning the use of NetBEUI with some databases)Quote:
Originally posted by The bear:
<STRONG>If the server is having problems with DHCP then the computer cannot obtain a user name.</STRONG>
No, it can't obtain an IP-adress - not a username (but still you can set an IP yourself)
<STRONG>If it has a specific address matching the servers first three strings and matching the subnet mask and the network goes down, the workstation can communicate with other workstations if the server goes down (Provding other clients are set-up the same way).</STRONG>
That's only the simplest of the simple setups. TCP/IP adresses consist of 4x8Bits ... and an IP-adress bitwise AND-combined with the netmask equals the network-adress...
If the network-adresses from one another IP matches then they don't need to be routed - if not, they can still be routed to one another by adding for example static routes - that's the way it works...
<STRONG>This is a good way to set-up the network if it is small and managable. If you are setting up a large network and have no way of keeping records of the address's I would suggest seting up the DHCP.</STRONG>
You're right with suggesting DHCP, but you still have to keep record of it and plan carefully in big networks...
<STRONG>NetBEUI - ... Over a 10/100 network this protocol is good.</STRONG>
If you have to route via WAN/VPN/Internet/whatelse you may not use this protocol as it has no Layer3 functionality - only bridging is possible.
I hope coxswain will reply sometimes... if not I'd like this topic to be moved to tech-to-tech (or be closed, if you mods feel, that we don't talk about the topic any more)
NetBeui broadcasts itself increasing your network traffic, we use tcp/ip, but Some applications, namely Hp scanner sharing software reqiured netbeui as it refuses to work otherwise, anyway to the prob
make sure that your client for M$ networks has your domain you want to login to, also check your network card see if there are any lights, sometime the most simple checks save alot of time, I did a machine that worked fine in the lab, but when I got it onsite, the network card was goosed, if your using UTP, are the points looped?, is your cable goosed? try a fluke tester if available, I could go on forever but you get the gist....
C'ya
Back to the original problem of not being able to browse the network. On windows millennium assuming the protocols are the same on client and host, ip address, subnet mask, etc. are all setup correctly, I would take a look at the the Browse Master setting in the File and Printer Sharing Properties in the Network Configuration Box. On an NT network, the NT machine should be configured the be the browse master, and the Millennium box should have the setting set to disabled or automatic. Also you want to make sure you have enabled file and printer sharing on the Millennium machine and are sharing a folder to be able to see yourself on the network.