Networking windows 2000 pro

Brien M. Because of the large volume of e-mail he receives, it's impossible for him to respond to every message. However, he does read them all. When you double-click this icon, it opens a folder containing network and dial-up networking icons. These icons are organized similarly to those in the Printers folder, with each icon representing a unique connection, as well as an icon that you can double-click to add a new connection. In this case, each icon represents a network or dial-up networking session.

Simply double-click the icon called Make New Connection to create new network or dial-up networking connections. Windows then launches a wizard that guides you through the process. You can use the individual connection icons to review or modify connection properties. Laptops and disappearing networking icons Laptop computers behave a bit differently.

On a laptop system, the Network And Dial Up Connections window would still contain the Make New Connection icon, but it would probably also contain one or two icons related to dial-up networking. One icon might be used to connect to an Internet service provider, while the second icon might allow a dial-up connection to a corporate RAS server. As shown in Figure A , the first dialog box asks you to select the type of activity you want to perform.

Figure A Use Ncadmin. Figure B Ncadmin. Figure C The Target Workstation Configuration dialog box lets you choose the type of floppy, network client, and network adapter card to use. Editor's Picks. The best programming languages to learn in Check for Log4j vulnerabilities with this simple-to-use script. Windows 7 Networking. Sign in to vote.

Windows 7, Build with home workgroup. XP computers browse and files no problem both ways. To Windows Pro, failure with Username and Password required and nothing accepted. Facts: Can ping the computer; can see and browse to the 7 computer; workgroup name is the same on all computers; username and password is the same on all computers.

Something not right on the Windows 7 computer or the Windows computer? Monday, June 8, PM. I gave up after too many hours. But in going back to Vista Home Premium bit, I struggled with some of the same issues. I am going to try again with some new understandings. But at the suggestion of one blog, turning off the Norton firewall and turning on the Windows firewall was the trick. For both OS's, you have to make the network private, share and not require a password.

Didn't work. I am hoping these tricks will work on Windows 7. Tuesday, June 9, PM. I'm back. Windows Vista Home Premium bit installed and running perfectly. Home network with XP-Pro and Windows Pro all connected and seeing and sharing in all directions. Printers installed on one of the Windows machines -- I know, dump the Windows computers "appear" in the lower map of network computers correctly named.

But if you try to connect to either of them, you get asked for a UN and PW, and there is no way of getting around this demand. I have tried all the permutations believe me. I have used my cable tester and found no problems with the cabling. Anyone have some ideas on what the problem could be? Well it is now on the network. I wish I could give you a reason why, but there isn't a good one. Here's how I got it to start working:.

Can you get a ping response from the local host? Just a double check - Windows required reboots for a lot of things that XP and higher don't. After installing the NIC did you reboot? I can't remember if each of those needs a reboot or not, it's been a while since I've touched , but it sure couldn't hurt.

Go into the managed switch or the NIC on the machine and change the value of "auto-negotiate" on one or the other. You want to set it to depending on the switch and card or Full duplex or Half Duplex. I had experienced this many times in the past. Thanks for all the suggestions. I can get back on the machine Friday, when it is not being used for production. This gives me tons of ideas to try. Need to try and ping the localhost, there is not keyboard, just a machine control so that will require copying the ping command to a floppy and copy pasting.

DHCP is working everywhere else on the network. I did try and change the negotiation, but only from auto to full. I will try other options. Well, I just got a few minutes on the machine. I can ping local host, the IP I statically assigned, but nothing else. Changed the negotiation rates.