BladeRnR
23-10-2003, 08:12 PM
I'm sure almost all of you have had a Network problem and know how frustrating they can be to fix it. You do the basics - Ping, IPConfig, Check Protocols, Check IP's, try Static IP's, DHCP allocated IP's - you know the drill. When you want something fast off another computer and you're in a (Fairly) closed Network, security doesn't have to be as strict. So you use Simple File Sharing to get the job done and worry about adding Users and making it tighter later on.
So that's just what I did recently. Spring is here so it was time for a format of both mine and my Bro's computers. Formats went perfectly and in 2 days we were Formatted, Installed & Imaged with a new Backup. Now my Bro needed some files so out came the LAN cable and we hooked up. Pinged ourselves and remote via NetBIOS name and IP. No problem - full comms. Allocated shares to a couple of our drives and we were off - but not quite.
We'd navigate to each other's drives using via Explorer using \\<remote share> and then click on the share. Nothing - the busy mouse would start going crazy then Explorer would fail to respond. We couldn't even look at our OWN shares let alone each others! No matter what I tried from my bag of knowledge worked. 3 days later I was still trying. New Cat 5 cable, different hubs - everything. Reviewed the Event Log extensively and I saw errors in there that would make a Network Admin shudder. How could a simple peer-to-peer Network give anyone so much trouble? I trawled Microsoft's Newgroups looking for answers and nothing made sense given my scenario. The only way to resolve this was the old fashioned way - inch by inch. So I formatted again.
So first thing I do when I boot into a fresh install of Windows is share C: Drive. Wham - I could see the share. Right - this was either software that was doing this or a Service we were turning off. Bit my bit and put everything back on. The last thing I do with any build is tweak it with TweakXP Pro and TweakUI. Everytime I put new software on I would test the share. It worked right up until I put on....TweakXP Pro and applied my usual tweaks. huh? I took TweakXP Pro off and my share worked again. uhuh. Put TweakXP Pro back on and had 2 windows up - TweakXP Pro and Explorer looking at my share. I'd apply a tweak and test my share. You know what it ended up being? TweakXP Pro Ad Blocker! Yep! As soon as I disabled it locally and remotely the shares were there. I've since E-mailed Totalidea Software and they sheepishly replied 2 days later they have a bug :cry: as they replicated the problem themselves.
The moral of this story? Computer problems are sometimes caused by totally unrelated issues. If you look through a typcial WinXP/Win2K Event Viewer you'll see all kinds of bizarre EventID's setting you off on the wrong course of action. One of the best ways I've found in solving a Computer problem (And this goes for my Professional job as well) - find out what changed. The only way you can do that sometimes is to go back to a vanilla state and see if it works then. If it does then something that's coming AFTER is causing the problem.
And last of all you never stop learning :)
Cheers
Blade
So that's just what I did recently. Spring is here so it was time for a format of both mine and my Bro's computers. Formats went perfectly and in 2 days we were Formatted, Installed & Imaged with a new Backup. Now my Bro needed some files so out came the LAN cable and we hooked up. Pinged ourselves and remote via NetBIOS name and IP. No problem - full comms. Allocated shares to a couple of our drives and we were off - but not quite.
We'd navigate to each other's drives using via Explorer using \\<remote share> and then click on the share. Nothing - the busy mouse would start going crazy then Explorer would fail to respond. We couldn't even look at our OWN shares let alone each others! No matter what I tried from my bag of knowledge worked. 3 days later I was still trying. New Cat 5 cable, different hubs - everything. Reviewed the Event Log extensively and I saw errors in there that would make a Network Admin shudder. How could a simple peer-to-peer Network give anyone so much trouble? I trawled Microsoft's Newgroups looking for answers and nothing made sense given my scenario. The only way to resolve this was the old fashioned way - inch by inch. So I formatted again.
So first thing I do when I boot into a fresh install of Windows is share C: Drive. Wham - I could see the share. Right - this was either software that was doing this or a Service we were turning off. Bit my bit and put everything back on. The last thing I do with any build is tweak it with TweakXP Pro and TweakUI. Everytime I put new software on I would test the share. It worked right up until I put on....TweakXP Pro and applied my usual tweaks. huh? I took TweakXP Pro off and my share worked again. uhuh. Put TweakXP Pro back on and had 2 windows up - TweakXP Pro and Explorer looking at my share. I'd apply a tweak and test my share. You know what it ended up being? TweakXP Pro Ad Blocker! Yep! As soon as I disabled it locally and remotely the shares were there. I've since E-mailed Totalidea Software and they sheepishly replied 2 days later they have a bug :cry: as they replicated the problem themselves.
The moral of this story? Computer problems are sometimes caused by totally unrelated issues. If you look through a typcial WinXP/Win2K Event Viewer you'll see all kinds of bizarre EventID's setting you off on the wrong course of action. One of the best ways I've found in solving a Computer problem (And this goes for my Professional job as well) - find out what changed. The only way you can do that sometimes is to go back to a vanilla state and see if it works then. If it does then something that's coming AFTER is causing the problem.
And last of all you never stop learning :)
Cheers
Blade