supersunbird
Honorary Master
Hey, try netbeui 
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
WindowsXP networking issues
- Thread starter The_Unbeliever
- Start date
The_Unbeliever
Honorary Master
Netbeui won't work as packets are sent out, but not received.
Also, email uses TCP/IP and not netbeui...
We're on a domain (crAptive directory) and it depends on tcp/ip as well...
It is worth a try tho... if it'll save me the reinstall hassle... but then again...
Device Manager says everything is peachy...
I don't believe it as there is a problem.
'nyways, Knoppix saved the day with the ability to make a backup of the data on the hard drive.
Tomorrow I'll just pop in the restore CD and get rid of this silly bugger once and for all...
Also, email uses TCP/IP and not netbeui...
We're on a domain (crAptive directory) and it depends on tcp/ip as well...
It is worth a try tho... if it'll save me the reinstall hassle... but then again...
Device Manager says everything is peachy...
I don't believe it as there is a problem.'nyways, Knoppix saved the day with the ability to make a backup of the data on the hard drive.
Tomorrow I'll just pop in the restore CD and get rid of this silly bugger once and for all...
Last edited:
The_Unbeliever
Honorary Master
Oh, and finally, last, but not least, a big thank you to all who bounced some ideas around here.
This one's got me positively foxed as this is the first instance of a "corrupt" TCP/IP stack (or something like it) I've seen on a WinXP box...
In Win98 the easy way out was to uninstall TCP/IP completely, reboot, then reinstall it - and it worked.
Wonder what Vista'll be like... *shudder*
I believe in sharing your problems with the world as somebody might have the same problem out there, and will save you the hassle and stress of finding the problem, and will also try to help out with other people's problems (if I can).
Regards
His Ookishness
This one's got me positively foxed as this is the first instance of a "corrupt" TCP/IP stack (or something like it) I've seen on a WinXP box...
In Win98 the easy way out was to uninstall TCP/IP completely, reboot, then reinstall it - and it worked.
Wonder what Vista'll be like... *shudder*
I believe in sharing your problems with the world as somebody might have the same problem out there, and will save you the hassle and stress of finding the problem, and will also try to help out with other people's problems (if I can).
Regards
His Ookishness
Try "WinSock XP Fix" for a last effort. Worked once for me.
http://www.snapfiles.com/get/winsockxpfix.html
http://www.snapfiles.com/get/winsockxpfix.html
SecretCode
Senior Member
Tomorrow I'll just pop in the restore CD and get rid of this silly bugger once and for all...
Meaning a reinstall? Best thing, but ...
Bugger.
bekdik
Honorary Master
Change the auto device setting on the device setting on the network connections to 100MB full duplex (or the same speed as the working machine). Sometimes the auto setting doesn't work - normally the problem is in speed /duplex setting.
The_Unbeliever
Honorary Master
Problem is fixed - buggery problem.
What I did is :
1. Backed up data.
2. Did an reinstall from the WinXP CD
*go through the stuff normally
*skip the rescue console
*proceed as if you're doing a clean install BUT elect to repair the windows installation... this will keep intact most programs and data.
If you do a full install (overwriting everything) then it's your problem, not mine.
This will delete some files and replace these with original, uncorrupted files.
Seems fine so far now... (touch wood)
My thought is that a bad sector happened, and got remapped, and with it, a crucial key part of the TCP/IP stack as well. *sigh*
What I did is :
1. Backed up data.
2. Did an reinstall from the WinXP CD
*go through the stuff normally
*skip the rescue console
*proceed as if you're doing a clean install BUT elect to repair the windows installation... this will keep intact most programs and data.
If you do a full install (overwriting everything) then it's your problem, not mine.
This will delete some files and replace these with original, uncorrupted files.
Seems fine so far now... (touch wood)
My thought is that a bad sector happened, and got remapped, and with it, a crucial key part of the TCP/IP stack as well. *sigh*
Last edited:
the brute force solutions
I had a problem yesterday where a user couldn't log into MSN, this was despite her pc having direct access to the net via a rule on the firewall. No firewall software installed, XP firewall disabled. The troubleshooter said key ports blocked
Solved it by creating a new local user account, but a repair was the next step...
I had a problem yesterday where a user couldn't log into MSN, this was despite her pc having direct access to the net via a rule on the firewall. No firewall software installed, XP firewall disabled. The troubleshooter said key ports blocked
Solved it by creating a new local user account, but a repair was the next step...SecretCode
Senior Member
Glad to hear it's fixed, but I would blame a registry ****up - ie Microsoft's fault not a hardware fault!
The_Unbeliever
Honorary Master
Tried that as well - no go... was only the windows reinstall which fixed things good and proper.