:|Hey everyone,
I need some help with a networking problem, because for once I'm stumped. My uncle bought a new computer a few months ago, and finally decided to network his new computer with his old computer. He did this via a 25 foot long crossover cable from one ethernet card to the next (I confirmed that it was indeed a crossover). The host computer servicing the internet is in the basement in his office, and the client is in his room on the second floor. The cable passes through a couple of inches of ciment, which is what my uncle says he had to drill through to pass the cable. Both machines are running windows xp and have all the standard protocoles installed (TCP/IP, Client for Microsoft Networks, File and Printer Sharing), both computers are in the same workgroup (in this case, simply 'home'). Both computers have an IP address assigned in the the 192.168.0.X subnet, and I even assigned 192.168.0.1 to the host computer. So as you can see, nothing special going on here, just your regular network.
Here's the breakdown:
From the Host Computer, I can:
- Ping the client PC (physical and protocals seem fine)
- Connect to the Internet (usb)
- Access the client PC's shared folders and files (file and printer sharing's working)
However,
From the Client Computer, I can:
- Do pretty much nothing
The client systematically refuses to ping the host computer, or access its shared resources.
One thing to note is that I did try turning off all firewalls (disconnecting from the internet before), and I still had no success.
I then reanbled the firewall (McAffee's, not Microsoft's), and attempted to ping the host again. This time I accessed the firewall's logs and confirmed that did indeed receive a ping request from the said client. I made sure the client's IP address had authorized access to the host machine and tried again. This time the IP showed up in my logs in green, yet the client still hasn't received a reply.
I searched the web and tried things like ensuring that NetBIOS over TCP/IP was enabled on both machines, confirming that the Computer Browser (service) was started, and everything looked picture perfect.
So PLEASE TELL ME that someone has been in my shoes before. I know I've seen it, but I can't recall for the life of me what was done to fix it.
Thanks for your help, even if it was just taking the time to read my lengthy message hehehe
-- Doc
I need some help with a networking problem, because for once I'm stumped. My uncle bought a new computer a few months ago, and finally decided to network his new computer with his old computer. He did this via a 25 foot long crossover cable from one ethernet card to the next (I confirmed that it was indeed a crossover). The host computer servicing the internet is in the basement in his office, and the client is in his room on the second floor. The cable passes through a couple of inches of ciment, which is what my uncle says he had to drill through to pass the cable. Both machines are running windows xp and have all the standard protocoles installed (TCP/IP, Client for Microsoft Networks, File and Printer Sharing), both computers are in the same workgroup (in this case, simply 'home'). Both computers have an IP address assigned in the the 192.168.0.X subnet, and I even assigned 192.168.0.1 to the host computer. So as you can see, nothing special going on here, just your regular network.
Here's the breakdown:
From the Host Computer, I can:
- Ping the client PC (physical and protocals seem fine)
- Connect to the Internet (usb)
- Access the client PC's shared folders and files (file and printer sharing's working)
However,
From the Client Computer, I can:
- Do pretty much nothing
The client systematically refuses to ping the host computer, or access its shared resources.
One thing to note is that I did try turning off all firewalls (disconnecting from the internet before), and I still had no success.
I then reanbled the firewall (McAffee's, not Microsoft's), and attempted to ping the host again. This time I accessed the firewall's logs and confirmed that did indeed receive a ping request from the said client. I made sure the client's IP address had authorized access to the host machine and tried again. This time the IP showed up in my logs in green, yet the client still hasn't received a reply.
I searched the web and tried things like ensuring that NetBIOS over TCP/IP was enabled on both machines, confirming that the Computer Browser (service) was started, and everything looked picture perfect.
So PLEASE TELL ME that someone has been in my shoes before. I know I've seen it, but I can't recall for the life of me what was done to fix it.
Thanks for your help, even if it was just taking the time to read my lengthy message hehehe
-- Doc
Facebook
Twitter