Networking HELL

We had similar problems ,many moons ago.

Eventually disable all ,power saving and ACPI ,anything has to do with power management and power saving on every PC on the network.from bios setup and windows.

Problems went away
 
Last edited:
I've had this one - was rediculous.
Turn on NetBios over TCP on the faulty computer, and on the server you're having difficulty getting hold of.
TCPIP Protocol -> Properties -> Advanced -> WINS -> Enable Netbios over TCP.
This is a fallback option but it will solve the problem. I am almost 100% sure.
 
Gooku and Stoke, I will try that 2moro and let you know. Ive disbaled the powersaving already on the NIC but not all the powersaving of all the pc's.

I really hope that this works. Thx ALOT!
 
stoke said:
I've had this one - was rediculous.
Turn on NetBios over TCP on the faulty computer, and on the server you're having difficulty getting hold of.
TCPIP Protocol -> Properties -> Advanced -> WINS -> Enable Netbios over TCP.
This is a fallback option but it will solve the problem. I am almost 100% sure.
Click to expand...

Can you explain to me why this would work? or resolve the problem?
 
Not a Bad idea, but then they'll have to but Win2000, what about Win98? They do have a original Copy of that
 
Perdition said:
I think if you own XP Pro you can run Win 2000 under the same license
Click to expand...
M$ might well disagree with you there, but in the interests of eliminating the possibles, I would give that a try if all else fails.

If it is a weird thing that persists after an XP reinstall, and with different NICz then maybe it's a problem in the BIOS - something that confuses XP. Perhaps try resetting defaults & see if the problem still happens.
 
IC> will try that Bios suggestion this morning. The other thing is, at anyway other network ( personal home Network ) it runs without any problem.
 
Ok, the other possibility is a conflicting Group Security Policy - between W2K and XP - something that causes XP to lock itself out or to be locked out by W2K. I assume that the machines are part of a domain that is setup on the W2K server?
 
Yes!

stoke said:
I've had this one - was rediculous.
Turn on NetBios over TCP on the faulty computer, and on the server you're having difficulty getting hold of.
TCPIP Protocol -> Properties -> Advanced -> WINS -> Enable Netbios over TCP.
This is a fallback option but it will solve the problem. I am almost 100% sure.
Click to expand...

For some reason, when i enabled NetBios, it kept working. It has not lost connection for 4 hours. Thx to all who helped and for all or ur ideas, i tried then all.

You guys rock! Would not have fixed it without you!
Cheers
( just tell me when i can help with something )
 
bismay said:
For some reason, when i enabled NetBios, it kept working. It has not lost connection for 4 hours. Thx to all who helped and for all or ur ideas, i tried then all.

You guys rock! Would not have fixed it without you!
Cheers
( just tell me when i can help with something )
Click to expand...

Are you sitting behind a GOOD firewall with that NetBios loose on your network. NetBios is not renowned for security!
 
venterap said:
Are you sitting behind a GOOD firewall with that NetBios loose on your network. NetBios is not renowned for security!
Click to expand...
Bismay, venterap speakada troof there, I would disable that ASAP, and look towards DHCP server settings for an answer - if I recall correctly from an earlier post, you have a router dishing out intranet IPz, correct? Is there a setting for Domain name suffix?
 
Okay - NetBios over TCP is dangerous.

An attacker could open a NBT Pipe to just about anything, and Browse the Computer List, Open a Named Pipe to SQL Server, Open a NonSecured pipe to the c$ share and implant itself using "Logon As" ... Yip pretty bad.

One step at a time please.

When NetBios solves the problem, in my experience, somebody has installed Norton AV + FW somewhere, and then not properly uninstalled it. Goto the Norton site and find the "remove all traces of norton" utility and run it on server and problem client.

I had this carp with a version of norton that came bundled with the OS in 2003. It's impossible to fix, just remove it and install the later version which is not so buggy.

Be like me - BLAME NORTON !!!!
 
stoke said:
Okay - NetBios over TCP is dangerous.

An attacker could open a NBT Pipe to just about anything, and Browse the Computer List, Open a Named Pipe to SQL Server, Open a NonSecured pipe to the c$ share and implant itself using "Logon As" ... Yip pretty bad.

One step at a time please.

When NetBios solves the problem, in my experience, somebody has installed Norton AV + FW somewhere, and then not properly uninstalled it. Goto the Norton site and find the "remove all traces of norton" utility and run it on server and problem client.

I had this carp with a version of norton that came bundled with the OS in 2003. It's impossible to fix, just remove it and install the later version which is not so buggy.

Be like me - BLAME NORTON !!!!
Click to expand...

But why is it only that pc out of 8 pc's that doing this?
 
Okay - monday's almost over - got most of me brain back.

The norton thing was theory A.

Theroy B:
I'd bet that that one stupid machine was once placed onto a proper windows domain.
Now the domain controller r gone, and every now and then it still looks for it, despite the fact that you specifically said - belongs to a workgroup. NetBios does not care about Windows Domain Authentification, so it ignores that kind of rubbish, and passes straight through.

Check if NetLogon service is running on that machine. If it is - stop it - and disable it - but it's only part of the problem, and you should find and follow the steps from MS to configure the machine so that it's not part of the domain. The problem is that : Step 1 = Logon to the pc into the domain. LOL. Now that the domain is gone - you're stuffed.
Probability that this is the cause = 54%.

I have 3 more useless theories - but I don't think that they're even worth mentioning.

Otherwise, run with NetBios enabled and keep an eye out for strange behaviour - which I doubt will ever actually happen, unless your user is a mad downloader. :)
 
Luckily not a mad downloader, only use MSN and Vodacom.co.za alot. Remember that i did use a clean copy of winXP on another pc ( my personal machine ) and still there was this problem. So far its been running the whole of Sunday and today without any errors.

I really do appreciate all the reply's i get! you guys really help alot. The enable netbios is just a fallback, the network should not be running with a setting on a network like this, for obvious reasons.

But until i found the real or solution im happy. I don't really know what goes on on this network outside the office. I will try and get a map of the whole network, but i think that every PC's has a Static IP. The bigger part of the network is Wireless.
 
Okay - wireless users. Now there is something that can cause endless grief. :)
Stupid question - have you checked that machine's system event log for IP Address conflict errors?
Wireless is the main reason that we switched out network to the 10.10.80.* instead of 192.168.0.*, cos every now and then somebody would hop onto the wireless network, and cause a conflict (depends which way the wind was blowing ... LOL).

Just a thought.
 
interesting thing ur saying because there have 2 occasions where and IP conflict did pop-up..... Hmmm

What now?
 
Something else, what about if i install the old Protocol.... NetBEUI?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X