9 replies
by techkid
So the systems are connected and see each other but they are just slow right? Don't know exactly what protocols and what not you have/want running but here goes. For completeness I'll start from the beginning: Both have to have same Workgroup, Different computer names, TCP/IP using same network address, File and Print Sharing, Uninstall Microsoft Family Logon if it's installed and install Client for Microsoft Networks instead
Good luck
by johnjsdc
by faisalmasood
1) Uncheck the 'Logon to NT Domain' option in Client for MS Networks in Network Control Panel.
2) Try Obtain an IP automatically option. Windows will be assigned IP through Automatic Private IP Addressing (APIPA).
3) Use same workgroup.
by johnjsdc
by brent t
Make sure your are not trying to log into the NT Domain (properties of the Client for MS networks), also verify your shares are setup properly, the protocols you are using are fine. If the PC are slow, your cross over cable may not be done correctly. Tech Republic had a great doc available on cable wiring some time back, do a quick search on the site for it, if there is an issue with the cable you should see it quickly or if you have a cable tester use that.
Good Luck
by johnjsdc
by brianaaa12
In some instances two Full-Duplex NIC's simply won't communicate well using full-duplex. Disable auto-sensing and manually set them both for 10 mbs half-duplex, then test. If that seems to fix it, then crank them both up to 100 mbs half-duplex andtest again. If that works, try 100 mbs full-duplex and see what happens.
Regardless of the situation, I never use auto-sensing. I have wasted too much time chasing my tail to only find out that it doesn't always sense properly.
Brian
by johnjsdc
by johnjsdc
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending