Re: How set server for home network?

From: min (caomin111_at_hotmail.com)
Date: 05/19/04 

Date: Wed, 19 May 2004 07:48:16 -0400

Thank you for detailed instruction.
I changed the TCP/IP configuration on Win2k computer to Enable NetBIOS over
TCP/IP£¬ but when from win98 to access Win2k computer, it still ask for
password.

Where to set the password for win98 to access win2k ?

(Win2k can access win98)
Thanks!
Min

"Roland Hall" <nobody@nowhere> дÈëÓʼþ
news:%23bmfUBLPEHA.3300@TK2MSFTNGP09.phx.gbl...
> "min" wrote in message news:%23mYpxO7OEHA.4036@TK2MSFTNGP12.phx.gbl...
> : The computer network system is like this:
> :
> : Computer1, 2, 3 all connected to a hub. they are in the same workgroup.
> : The hub is connected to internet through a DSL modem:
> :
> : [computers] => hub => DSL modem=> ISP(internet server)
> :
> : What I want to do is let all computers have internet access, but also
can
> : share files and printers in workgroup.Meanwhile, I need IIS on one
> computer
> : just for program test.
> :
> : I installed win2k server on a computer, and all computers can access
> : internet, but the workgroup did not work anywhere.
> :
> : How can I set the win2k server in this system?
>
> Hi Min...
>
> First let me say, good job providing detail. We usually have to ask.
>
> Let's cover some basics.
>
> 1. The Internet uses only one protocol, actually a suite of protocols,
> TCP/IP. NetBEUI is not routable and since the net only supports TCP/IP,
> it's of no use on the net. You should only be running TCP/IP. However,
in
> Win98, this is actually NetBIOS over TCP/IP. Over implies it is wrapped
in
> an IP packet, sent to the target system, via the wire [cabling or
wireless],
> and unwrapped on the other end so the NetBIOS information can be used. On
> the Internet, this can also be done but most connections are just using
> TCP/IP.
>
> Since Win98 MUST use NetBIOS to communicate with other systems that it
logs
> into, the target system must also be configured with NetBIOS over TCP/IP.
> Your network settings will show this.
>
> Right click on My Network Settings on the desktop, select properties.
> Right click on your network interface, generally called Local Area
> Connection and select properties.
> Locate Internet Protocol (TCP/IP), in the components list and select
> [highlight] it.
> Click properties.
> Click the Advanced button.
> Click the WINS tab.
> Make sure Enable NetBIOS over TCP/IP is selected.
> Click OK to save and close each window [should be 3 of them], then click
> close on the last one.
> If it asks you to reboot, do that.
>
> Let us know if you can see the other systems [after installing and only
> using TCP/IP on the Win98 computers].
> This will not solve your Internet problem but will get you working
locally.
> You will need the same logon and password on each system that you try to
> connect to. You can create different users on the server and it can
connect
> using any credentials but Win98 can only connect via the credentials it
used
> to logon to the workstation. While you can have more than one, you would
> have to logout first and login as the other user.
>
> For your Internet connectivity, I suggest getting a SOHO router. I prefer
> Belkin over others but most any will do. It should be NAT capable, have a
> firewall, application support and have a web interface for configuration.
> Unless you are going to run AD (Active Directory) you can let the router
> supply the IP information for the workstations but you need a static IP
> address for the server.
>
> After installing a firewall, your local IP information will use private
> addressing, generally 192.168.0.x or 192.168.1.x, by default. x will
> generally be 1 by default for the router. Assign a static number to the
> server, outside the range of your IP pool for your workstations. If your
> router allows for 50 other connections (default for Belkin), then make
your
> server an address above that or reduce the 50 to something closer to what
> you have. I have less than 10 workstations so I reduced my pool to
address
> 10 and starting with 2. So, my server is .11 or 192.168.0.11. You set
this
> in your network settings on your server. There is nothing to tell the
> router about the server, other than if you want to run a web server on it.
> This will require you opening up port 80, routing it to 192.168.0.11 [if
> your server is set for address 11] and allowing the HTTP service.
>
> Your router can be set to get the IP information you are now getting from
> your ISP. If it is dynamic, it will happen when you plug the router in.
If
> it requires some specific configuration that you were sent by your ISP,
then
> you will need to configure the router per those instructions.
>
> Shout where you get stuck and we'll go from there.
>
> --
> Roland Hall
> /* This information is distributed in the hope that it will be useful, but
> without any warranty; without even the implied warranty of merchantability
> or fitness for a particular purpose. */
> Online Support for IT Professionals -
> http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
> How-to: Windows 2000 DNS:
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
>
>

Quantcast