• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

TCP/IP continually self destructs on home network.

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
The default installation of TCP/IP in WinXP is with NetBIOS enable.

However if it is not enforced by your DHCP server you can enable it manually.

Right click on your LAN Connection choose TCP/IP properties click on the Advanced (down right), and choose the WINS Tab.

:light:
 
I did that net config work with this result:

Computer name \\MJS-1
Full Computer name mjs-1
User name Mark J. Sherrell

Workstation active on
NetbiosSmb <000000000000>
NetBT_Tcpip_<B2E5BAFD-46E4-4043-874D-4424BAE8AF39> <0048548D6868>

Software version Windows 2002

Workstation domain MSHOME
Workstation Domain DNS Name (null)
Logon domain MJS-1

COM Open Timeout <sec> 0
COM Send Count <byte> 16
COM Send Timeout <msec> 250
The command completed sucessfully


Then I did the net config server, with this result:


Server name \\MJS-1
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb <000000000000>
NetBT_Tcpip_<B2E5BAFD-46E4-4043-874D-4424BAE8AF39> <0048548d6868>

Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time <min> 15
The command completed succsessfully

I hope this tells you something becaus It tells me jack!

Here's the strangest thing: one machinecan ping the other, but by IP adress only, the other cannot ping back at all!
 
You get me to do all that above then leave me hanging? 😀 I know patience patience......so little do I have!
 
If IPX/SPX works, go with that. Its about the same as adding NetBeui. Its just another protocol. Actually, sharing not working with TCP/IP is sort of good for security...meaning that you cant share over the internet and other internet users cant use your shares. Recommend you stick with IPX/SPX unless you just need to beat this thing.
 
Oops... my bad. Sorry for the blank post.

I'm not a total network wiz, but I've been maintaining a small one at work and a small one at home (using a D-Link router to share Roadrunner) for a couple of years now. My home netweork had several problems when first set up (all the computers were running ME at the time and file sharing was erratic). Most of the problems were eventually cured by going to fixed IP adresses. Have you tried fixed IPs??

Anyway, when I started converting some of the comps at home to Win XP Pro, things got a little stickier. I still used fixed IP addresses, but to get computers to show up on a home network I had to make sure they all were members of the same workgroup, and that they all had something set up to share on the computer (otherwise they might not show up on the workgroup list). And, of course, they won't show up if they're not turned on (I believe in WinME they sometimes showed up on the MyNetworkPlaces list even if they weren't turned on.

Then, in WinXP, you still have to drill down through "MyNetworkPlaces/ EntireNetwork/ Microsoft Windows Network" to see the shared computers. They don't necessarily show up under "My Network Places" directly.

So, if you haven't already, make sure all the computers are on the same workgroup, make sure they all have a folder set up to share, and make sure you drill down to the workgroup to see if they are there. By the way, I am using TCP/IP with NetBios set to default under WINS.

Good Luck.
 
Originally posted by: markjs
I did that net config work with this result:

Computer name \\MJS-1
Full Computer name mjs-1
User name Mark J. Sherrell

Workstation active on
NetbiosSmb <000000000000>
NetBT_Tcpip_<B2E5BAFD-46E4-4043-874D-4424BAE8AF39> <0048548D6868>

Software version Windows 2002

Workstation domain MSHOME
Workstation Domain DNS Name (null)
Logon domain MJS-1

COM Open Timeout <sec> 0
COM Send Count <byte> 16
COM Send Timeout <msec> 250
The command completed sucessfully


Then I did the net config server, with this result:


Server name \\MJS-1
Server Comment

Software version Windows 2002
Server is active on
NetbiosSmb <000000000000>
NetBT_Tcpip_<B2E5BAFD-46E4-4043-874D-4424BAE8AF39> <0048548d6868>

Server hidden No
Maximum Logged On Users 10
Maximum open files per session 16384

Idle session time <min> 15
The command completed succsessfully

I hope this tells you something becaus It tells me jack!
Click to expand...

well that looks good on one machine, how about the other?
 
Be aware that I said one machine can ping the other by IP only but the other cannot ping back!

hold on and I will post the other machines results quick as I can.
 
Originally posted by: markjs
Be aware that I said one machine can ping the other by IP only but the other cannot ping back!

hold on and I will post the other machines results quick as I can.
Click to expand...

something's not right then. if both computers cannot ping each other by IP address then we'll never get filesharing to work.
 
I know somethings not right!!!! DING DING DING DING!!! You win the grand prize! LOL...(please, I am just kidding, don't take it personal).

The question is what is wrong?!?!? Last time it took a complete windows reinstall to get things working again and the exact same thing happened again. I have up to date virus protection and everything.....Damn this is frustrating.
 
The first problem is win xp...it's crap with networks and overall!

Second, try removing all network adapters, uninstall tcpip all other protocols.

Can each of the pcs ping themselfs?
 
You may think I am nuts but have seen your problem a few times with Friends systems and it was a problem with their firewall software in every case. They all used Zonealarm and it broke for some reason and only one machine could ping the other but not the other way around and no file sharing but Internet worked on both systems. Shutting down Zonealarm solved it so we unilstalled and reinstalled Zonealarm and all was fine. Do you use Zonealarm? If not by any chance do you have the XP Firewall turned on? None of this may be your problem but I figured it could not hurt just in case. We never tried other Protocols as he wanted TCP/IP to work.

There is a Fix for TCP/IP in XP. It's here on Anandtech. Will go find it and post the link. It's in the Faqs by Andy Hui.

Hope this helps just in case.

Here is the direct link from Andy's link.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q299357

If something is wrong with your TCP/IP that should take care of it as it rebulids the whole thing including the registery.

Since your internet works on both machines it's not your Winsock. Ran into that the other night. This friend downloads everything that he sees and one piece has sypware which ruined his Winsock keys in the registery taking down his internet.
 
Originally posted by: Dennis Travis
You may think I am nuts but have seen your problem a few times with Friends systems and it was a problem with their firewall software in every case. They all used Zonealarm and it broke for some reason and only one machine could ping the other but not the other way around and no file sharing but Internet worked on both systems. Shutting down Zonealarm solved it so we unilstalled and reinstalled Zonealarm and all was fine. Do you use Zonealarm? If not by any chance do you have the XP Firewall turned on? None of this may be your problem but I figured it could not hurt just in case. We never tried other Protocols as he wanted TCP/IP to work.

There is a Fix for TCP/IP in XP. It's here on Anandtech. Will go find it and post the link. It's in the Faqs by Andy Hui.

Hope this helps just in case.

Here is the direct link from Andy's link.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q299357
Click to expand...




DING DING DING DING!!!! YOU DO WIN THE GRAND PRIZE!!! turning Zone Alarm off was not enough....It needed to be uninstalled entirely! Thanks a MILLION!!!!
 
I should have made that more clear. Even if you turn it off True Vector Monitor keeps running. Only way is to uninstall it completely.

Glad it worked.

If you reinstall Zone Alarm make sure you go to the Firewall/Zones tab and add the IP Address's of your network! Otherwise it will block networking between your computers.


 
Well Finally Good End.

A final Note.

In one of the Links posted here few days ago it was Highlighed Disable Firewall. I guess I did not realize that Disable Firewall can also be understood as as switch it Off (Fixed it Now).

In any case for future trouble: Free - Process Explorer.

This program let you see what is actually running and let you kill it.

Using it would show if any ?Switched Off? program still has part running in the background.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top