Slyke Posted August 5, 2008 Report Share Posted August 5, 2008 Here's a diagram of my network:This is a very strange problem.Computer 2:When I am on Computer2 and do a net view I can see:Laptop1NAS-001Computer2Computer1I can successfully ping all of these using these Netbios name and it returns their IP addresses and they reply.I can successfully connect to all of these computers (And NAS) except Computer 1. It says the network name can't be found. This is in windows explorer using \\computernameComputer 1:When I am on Computer1 and do a net view I can see:Laptop1NAS-001Computer2Computer1I can successfully ping all of these using these Netbios name and it returns their IP addresses and they reply.I can successfully connect to all of these computers except NAS-001. It says the network name can't be found. Yes, i can even connect to Computer2.Laptop:When I'm on the laptop and do a net view I get nothing except the laptop, but i can connect to all computers.What's going on here??????Edit:Also these results have now changed since yesterday. Computer2 says:"C:\Users\Username>net viewSystem error 6118 has occurred.The list of servers for this workgroup is not currently available"But still allows me to connect to all computers, except Computer1.Computer1 only detects Computer1 when doing a net view. Still can connect to all but the NAS.Laptop still connects to all, but still only sees it self.Would there be any way to force a netbios update through out the 192.168.1.0 network? Even if i had to type it in manually on each computer? I think this might help solve some problems. Quote Link to comment Share on other sites More sharing options...
Slyke Posted August 5, 2008 Author Report Share Posted August 5, 2008 Also now ping statistics are saying like loss=50% when pining Computer1 from Computer2. And i get the error: "0x80004005Unspecified Error"When using the IP address to connect to. Quote Link to comment Share on other sites More sharing options...
Slyke Posted August 5, 2008 Author Report Share Posted August 5, 2008 Don't worry.I figured it out.What was happening was for some unknown reason the Firewall on computer 2 was blocking the SMB ports from Computer1, but not form any other (Which is strange as I haven't touched the firewall).Though I still have the problem on Computer2 (Vista) with the 6118 error. Apparently my domain doesn't match my workgroup. Which is strange since I'm not on a domain :s. Quote Link to comment Share on other sites More sharing options...
homecomputeraid Posted August 5, 2008 Report Share Posted August 5, 2008 I'm not sure how to do this in Vista, but you might try changing the workgroup name to something else, then changing it back to the one you want. This might tell the computer it's not on a domain, and get it joined back to the workgroup. Quote Link to comment Share on other sites More sharing options...
Slyke Posted August 5, 2008 Author Report Share Posted August 5, 2008 Ah i solved this.I tried to copy a file over (It's size was +4GBs) and after about 30 seconds the vista computer would BoSD. It took me a while to find out why it was doing this as it hadn't done it before.I noticed that it only happened when i tried to copy a large file over the network (from or to the machine) or stream some sort of video.So after about 20 or so blue screens I noticed the ndis.sys file was the one the blue screen was reporting.So after a bit of googling I discovered that it was my network card drivers not liking my new Linksys router. Some other people had the same problem.So i upgraded my drivers and it fixed every problem that I had :).Thanks for checking up though. Quote Link to comment Share on other sites More sharing options...
homecomputeraid Posted August 5, 2008 Report Share Posted August 5, 2008 Thanks for letting us know! It's very helpful for people who experience similar problems in the future. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.