How to Connect Windows 98 & Linux to Windows Server 2000?
82022
Simple use samba, chk out:\n\nhttp://us2.samba.org/samba/what_is_samba.html\n\nhttp://www.troubleshooters.com/linux/samba.htm\n\nhttp://www.linuxheadquarters.com/howto/networking/samba.shtml\n\n--\nBalakumar Muthu\nhttp://i5bala.blogspot.com
1134442
http://www-128.ibm.com/developerworks/linux/library/l-radius/\nFor Linux\n\nSetting up Windows 2000 Radius to authenticate wireless 802.1x clients\n\nRequirements: \nWindows 2000 with Active Directory (latest service pack) Certificate server IAS server Access point with 802.1X capability, the following were used in this guide \nLinksys BEFW11S4 D-link DI-824vupWindows 2000 or Windows XP client with a wireless adapter (latest service pack) \n\nWindows 2000 Radius server setup:\n\nMake sure Active Directory and DNS are configured properly\n\nInstall the IAS and certificate server components from add/remove programs\n\nhttp://www.pctechnicians.ca/help/isainstall.jpg\n\nAfter the IAS and certificate server components has been installed successfully. Setup the server as CA root and register the ISA server with Active Directory.\n\nFor help on setting up the certificate server for automatic certificate allocation:\n\nClick Start, and then click Help\n  Click the Search tab, type the following text, and then click List Topics : \nconfigure automatic certificate allocation from an enterprise ca \nIn the Select topic list, click Configure automatic certificate allocation from an enterprise CA , and then click Display\n To register the Radius sever:\n\nRight click the RADIUS server and select the "Register in Active Directory" option.\n\nhttp://www.pctechnicians.ca/help/IASregister.jpg\n\nClick ok when you see this message\n\nhttp://www.pctechnicians.ca/help/ISA1.jpg\n\nNext right click the clients option and select create new client.\n\nhttp://www.pctechnicians.ca/help/ISAclient2.jpg\n\nName : <Access Point name> IP: <IP address of the Access point> Click Verify to make sure its the correct IP Client Vendor: Radius Standard Check the "client must always send signature attribute in the request" box Enter a secret key that will be exchanged between the access point and server\n\nhttp://www.pctechnicians.ca/help/IASclient.jpg\n\nEdit the remote policy to include Extensible Authentication Protocol on the Authentication tab Also add the group that you want to allow wireless access\n\nhttp://www.pctechnicians.ca/help/wlanpolicy2.jpg\n\nChanging the user properties in Active Directory:\n\nGive the user dial in permissions, or create a group and add the users to that group Change domain mode to native to enable the Remote Access Policy option\n\nhttp://www.pctechnicians.ca/help/wlanpolicy.jpg\n\nRadius client setup:\n\nD-link access point configuration:\n\nEnable 802.1X Encryption :enabled Server: W2k Radius IP Port : 1812 Radius secret : same as Radius server WEP enabled (optional)\n\nhttp://www.pctechnicians.ca/help/dlink.jpg\n\nLinksys access point configuration:\n\nWireless security : Enabled Security mode: Radius Radius Servers address: W2k Radius IP Port : 1812 Shared Key: same as Radius server Wireless encryption type : 64bits 10HEX\n\nhttp://www.pctechnicians.ca/help/linksys.jpg\n\nNote: Once the Radius Server and clients are setup, stop and start the IAS service and reboot the access point.\n\nWireless client setup:\n\nSelect the "wireless networks" tab from wireless network properties Highlight the access point in the available networks and click configure On the "association tab" change the network authentication to "Open" Data Encryption: WEP If WEP was enabled on the router and a KEY was set then enter the Key here if a WEP key was not specified on the access point then, check the "key is provided for me" option\n\nhttp://www.pctechnicians.ca/help/8021x1.jpg\n\nAuthentication tab\n\nEnable IEEE 802.1x EAP type: Select protected EAP (PEAP)\n\nhttp://www.pctechnicians.ca/help/WLAN2.jpg\n\nClick the properties button Authentication Method: Secured password (EAP-MSCHAPv2) Click the configure button Uncheck the windows logon name and password box\n\nhttp://www.pctechnicians.ca/help/802x12.jpg\nRight click the wireless icon and select the "View available wirele
266440
It's very possible.  Out of the box, Windows 2000 can be a DNS, DHCP, file and print server.  Just go to Add/Remove Programs -> Windows Components -> Networking services to add DNS and DHCP.  Right click on any installed printers or folders and choose Sharing and Security to share them out.  Finally, if you're on a domain, you can just install Exchange.  If you're not, you need to create a domain by clicking Start -> Run  and typing DCPROMO and pressing enter.  Then, follow the prompts to create a new domain (this will actually install DNS too if it's not set up already).  After it's installed and you've rebooted, you can just install Exchange and be ready to go.  If you've not purchased the software yet, though, you should consider Windows Small Business Server as it's designed to have everything running on one box.
1128682
That's Fine Choice... win 2000 will run comfortabally..... and why do you use Windows 2000 i know it's easy handling servers Since Microsoft has already released windows 2003 Server which is quite similar to windows Xp with windows 2000 Features and many more!
481866
for windows based client server:\n1- install windows xp on all of computers\n2- make a workgroup by defining ip addresses\n3- take a computer as server by installing windows server 2003 or 2000\n4- install "active directory" from windows server cd on your server\n5- when active directory installing you most naming your <domain>\n6- after installing active directory on your server, your server is a domain controller\n7- remember your <domain> name\n8- on the clients go to my computer properties and change workgroup to domain and name it as your domain name\n9- set gateway address of your clients as your server ip\n10- also set dns of client as server ip\n11- in server set gateway and dns as ip of your proxy server\n\nIt's Done. Enjoy :)
341386
I recommend that you get Kubuntu.  It has software built in that can handle Wi-Fi for a laptop.  The drivers for most, if not all hardware, is built into the Linux kernel, so most of your stuff will work, assuming your computer is fairly new, like 2001 or younger.  I'm using Kubuntu on a Pentium II 233MHz desktop right now, and I dual boot it with Windows 98 Second Edition without any problems.\nIf you have an other questions, feel free to email me at pritesh_patel52@yahoo.com
162876
If you got Windows 2000 Server or 2003 Server OS, than use the Routing functionality, if you just want to share internet connection ,enable ICS = Internet Connection Sharing on Win XP
999276
It can be easily done by using SMB(samba server) on linux machine. Just add your machine physically(TCP/IP LAN/WAN) and then install Samba server if its not installed. Thats it! .. Read below resource for detail and requirments. Good luck!
693319
Well, depending on the OS you want to use ie, Windows Server or a Linux / UNIX Distro, there are allot of resources for setting up a server, there are many different types of servers as well, web server, ftp server app server, mail server, dhcp / dns, and so on. \nI would suggest a Linux / UNIX distro running Samba 3, that will allow communication between Windows and UNIX. \n\nhttp://www.freebsd.org is a good reference with allot of tutorials on how to accomplish what you need. best part, it is free.
688318
if u have windows server 2003 .\ndo follwing steps,\nstart-prgarms-Administrative tools-Remote desktop then follow the steps.\n\nif u use XP , u can use remte assistant for that.
963087
for win xp is:-\n\n1. click start menu > my network places > on the left panel, click "view network connections" > right click on "local area connection" > click "enable".\n\nfor win 98:- (important:- better get a good network technician to help you in win 98 network as it is very very risky!!!!!!!)\n\ncheers and good luck!\n\nmercury of love
982411
Try this ....\n\nMS-DOS 6.22\n\nThe DOS program that lets users send data between computers is called INTERLNK (pronounced "interlink"). It's a file transfer program that essentially lets one computer access the hard drive and printing functions of another computer. It won't let computers talk through the Internet using modems, nor will it lets users run DOS-based programs between computers. It's merely a way to transfer data. \n\nYour first move is to make sure INTERLNK is in the Config.sys file. If it's not in the file, place an Interlnk.exe file there by adding a DEVICE= statement. Type edit config.sys at the C> prompt. On one of the lines in the text window that appears, enter device=c:&#92;dos&#92;interlnk.exe. There will probably be other DEVICE= statements in this section so you have some sort of pattern to follow. \n\nAs soon as INTERLNK is installed, the program will begin looking to connect with another computer, one that is running Intersvr.exe, which is server software. (We'll talk about this more in a minute.) If the INTERLNK PC finds a companion, it will display a screen that looks like this:\n\n\nMicrosoft Interlnk Version 1.00\n\n\nPort=Com1\n\nDrive letters redirected: 5 (D: through H:)\n\nPrinter ports redirected: 1 (LPT3:)\n\nThe DEVICE=C:&#92;DOS&#92;Interlnk.exe statement adds one half of the PCs to our two-sided computer linkup. This part of the connection will be the client side, a program that's dependent upon another computer for a major part of its service. This other computer is the server. It will do a majority of the processing between our two computers so make sure that of the two PCs you're connecting, the stronger machine is the server. On this PC, you'll load the server software by typing intersvr at the C> prompt. \n\nYou must reboot both computers before the software will be fully installed. Once the client and server software is loaded, the programs will be looking for each other, usually on communications port 1 (COM1). If you've plugged the serial connector into a ny port other than COM1, type /com2 (or whichever COM port it was) at the end of the client DEVICE= statement. The complete client's DEVICE= statement for the new COM port will read "DEVICE=C:&#92;DOS&#92;Interlink.exe /com2". \n\nOne drawback to INTERLNK software is that the server PC can do nothing while the client has access to it. The server PC merely serves the client-side computer. This means you can't access files or print from the serving computer. On the client side, however, you'll have three new drives: D:, E:, and F:, which correspond to the A:, C:, and D: drives of the server. Access them with normal DOS commands.\n\nNOTE: You will need a PC-to-PC serial cross cable.\n\nPin --- Pin\n1 --- 1\n2 --- 3\n3 --- 2\n4 --- 5\n5 --- 4\n6,8 --- 20\n7 --- 7\n20 --- 6,8\n\nSee here for more info on the cabling:\nhttp://www.arcelect.com/rs232.htm
170410
If Windows XP try this site...\n\nhttp://www.microsoft.com/windowsxp/using/networking/expert/bowman_02april08.mspx
160674
You can setup your linux machine as a samba server. your samba server can even work as a domain controller for your network which can also contain windows clients. You can also use just ssh,telnet or ftp(your linux server should be ssh,telnet or ftp server respectively). For ssh you need to install putty.\nYou can get putty from here http://www.atlantawebhost.com/putty/\nWinscp is also an option. Just figure out one according to your need.
1070645
check the connection. (i doubt its connection unless short on motherbord)\nwhen that checks out fine uninstall the drivers. then restart the computer. windows 2000 shoul detect the cd and dvd drivers.\nwhen that works, give me the 10 points
24526
you should use tn3270 protocol to connect to mainframe , for this reson there are many software like extrawin
86994
Have patience, run Network Configuration Wizard, restart the computer. MAKE SURE YOU SET THE SAME WORKGROUP NAME FOR BOTH STATIONS!! Otherwise it will take Windows forever to change recognize it after you have changed it. But just have patience, once Windows XP came along networking got just a little bit harder to get started as opposed to WIN98.