WHY WHY WHY?! Network "flukes" always plague me, but professionals act like they don't exist...

[CZroe]

Certain PCs can't connect to cetain PCs FOR NO REASON...
Certain PCs can't browse the network without reinstalling the OS FOR NO REASON...
Certain PCs can't lease an IP address FOR NO REASON...
NIC bridging that only works for a few minute FOR NO REASON...
Blah blah blah blah.

I've NEVER been able to just plug it all together and configure it and have it work.

Just today, I was working on a guy's network. He just bought a Dell server with Windows2003 for his business (a print shop). He didn't know what he was doing and was just following the wizard that pops up when you first run an MS server OS ("What do you want your server to do?"). I found that he was using a router as a hub and had put two NICs in the server simply because MS' ICS wizard had gotten to him first (Though he never got it working that way). I connected the cable modem to the router and configured it to share the Internet connection and provide DHCP. I set all the PCs to obtain their configurations through DHCP.
But one PC would have none of it. IP config would show what was clearly an "IP Autoconfiguration Address," but it only said "IP Address" It was set to obtain through DHCP. I ran a repair operation and uninstalled and reinstalled the adapter and it wouldn't work. The hub (10bt!) worked because the PC next to it was on the network and browsing online. We swapped ports, swapped cables, and still got nothing with a /release + /renew. I tried manually configuring the IP, Subnet, Gateway and DNS and it was able to get online just fine. Hmm.

I went back to the Linksys router, unplugged it and plugged it back in. Tada! It works. IPCONFIG /renew picks up a DHCP lease. After all that hair pulling and barking up the wrong tree (The cable plant was a bitch, yet this is actually the easiest such problem I've encountered this year).

And then none of them could "see" the domain. DAMN! I think that's a problem with his wizard-driven server configurations done before I got there, so I'll look back into it tomorrow.

Will someone at least admit that they run into the same flukes I do?! Or do I just have bad luck? When setting up my wireless router, I had a similar issue that was only solved by powering EVERYTHING down and turning on one at a time. Modem, Router, PC.

Every certified person I know automatically thinks I'm doing something wrong and refuses to believe the stuff is flaky just because it's all "Name brand" and "Conforms to standards"

 

[spidey07]

in all honesty, no. I've never had those problems. As long as addressing and everything is setup correctly it works.

Unless of course you have a piece of defective network gear which does happen.

 

[exx1976]

I'm gonna have to agree with Spidey... I can't tell you how many times my PC tech calls me up and says "I can't figure this out", so I go there and fix it, and he says "Dude, that is EXACTLY what I just did!" Obviously not, or it would have worked...

 

[spidey07]

As long as the foundation of any network is built solidily it all works like a champ.

1) good cables/plant
2) Working network gear conforming to all ethernet standards, like not having loops, etc
3) solid nework services like dhcp and dns, making sure DHCP is providing all the proper info
4) PCs that haven't had their network settings garbled beyond belief like reinstalling adapters 10 times, randomly changing network and IP settings, etc.

 

[JackMDS]

Few Words Wizards, ICS, ICF Zero Configuration etc.

Wizards are like Yugo.

Yeah it will take to work for a while, but you are guranteed that sooner (rather than later) it will brake and you will not get to Work.


Most of the occurrences as described above are due to the use of Wizards and similar short cuts. It does not matter that at times it seems to work. It does changes in configuration to the system that (like the Yugo) sooner rather than later it will go bad.

Clean Install of WinXP with Manual configuration and no use of ICS ICF Zero Config, Wizards etc. rarely goes bad.


There are only 3 types of Wizards & ICS users.(By BobR)

1. Those that have had problems with it.
2. Those that are having problems with it.
3. Those that are going to have problems with it.

 

[chsh1ca]

CZroe, believe it or not, I know a lot of people with similar issues, and I regularly hear "Dude, that is EXACTLY what I just did", just like exx. I think the thing is, computers are like giant feral demonic wolves. If they smell your fear, they will eat you (not work for ya). If you just assume you know what you are doing, they shut up and behave, only to misbehave again 10 minutes later.

There's a lot of humour thrown into that analogy, but a touch of truth too. All I have to keep telling myself is to REMEMBER TO CHECK THE DAMNED CABLING! That's where 99% of the issues that frustrate me end up being.

 

[Fiveohhh]

Originally posted by: CZroe
Certain PCs can't connect to cetain PCs FOR NO REASON...
I connected the cable modem to the router and configured it to share the Internet connection and provide DHCP. I set all the PCs to obtain their configurations through DHCP.

And then none of them could "see" the domain. DAMN! I think that's a problem with his wizard-driven server configurations done before I got there, so I'll look back into it tomorrow.

they won't be able to see the domain unless your having your router give out the servers IP for DNS. Also make sure the Server is using itself for dns, and that the server is setup to be a DNS server.