Network = nothing
Ok this is related partly to this question https://www.experts-exchange.com/questions/20802031/WMI-problem.html
You don't need to read all the comments in that question but please read the question itself before responding here.
Nothing I tried including jumping over the moon fixed that problem not even a Repair install. Had to do a fresh install, even MS didn't have any thing on their sites that even came close to addressing the issue let alone any fixes.
Any way the fresh install cured part of the problem. What the current problem is that networking isn't working. Now when I did setup to connect to my Win2000 machine I got access denied due to permissions. Ok no problem I said I know what to do. Went to the Win2000 machine and set up an account to match the account on my XP machine. Rebooted both machines. Guess what neither machine can see each other now. It is like neither machine exists but XP did see the Win2000 machine long enough to know it was there when I first try to setup the networking, now nothing.
I have a cable modem that was just installed and it works fine on the Win2000 machine but all I get is 0's as an IP address when I ipconfig when the modem is hooked up to the XP machine. Now I know that the NIC and the cable modem are working. I tested this with a disk I have that has Win2000 on it. I booted to that disk on the XP machine hooked the NIC to the cable modem and connected to the Internet without nary a problem, ipconfig gave me IP address's.
Ok so the issue is with XP not the devices
I don't want to do a System Restore too many program registry settings will be lost and I don't want to spend many hours reinstalling the programs.
A Repair may work but not willing to go there just yet cause I figure this issue probably has an actual fix. I ran the network diagnoses as I stated in that other question and I am no longer getting the following so the fresh installed cured that problem.
===================
- Internet Explorer Web Proxy WMI Error FAILED
Unable to connect to WMI namespace 'netdiagnostics'
Computer Information
- Computer System WMI Error FAILED
Unable to connect to WMI namespace 'win32_computersystem'
- Operating System WMI Error FAILED
Unable to connect to WMI namespace 'win32_operatingsystem'
- Version WMI Error FAILED
Unable to connect to WMI namespace 'win32_operatingsystem'
Modems and Network Adapters
- Modems WMI Error FAILED
Unable to connect to WMI namespace 'win32_potsmodem'
- Network Adapters WMI Error FAILED
Unable to connect to WMI namespace 'win32_networkadapterconfi
- Network Clients WMI Error FAILED
Unable to connect to WMI namespace 'win32_networkclient'
===================
You don't need to read all the comments in that question but please read the question itself before responding here.
Nothing I tried including jumping over the moon fixed that problem not even a Repair install. Had to do a fresh install, even MS didn't have any thing on their sites that even came close to addressing the issue let alone any fixes.
Any way the fresh install cured part of the problem. What the current problem is that networking isn't working. Now when I did setup to connect to my Win2000 machine I got access denied due to permissions. Ok no problem I said I know what to do. Went to the Win2000 machine and set up an account to match the account on my XP machine. Rebooted both machines. Guess what neither machine can see each other now. It is like neither machine exists but XP did see the Win2000 machine long enough to know it was there when I first try to setup the networking, now nothing.
I have a cable modem that was just installed and it works fine on the Win2000 machine but all I get is 0's as an IP address when I ipconfig when the modem is hooked up to the XP machine. Now I know that the NIC and the cable modem are working. I tested this with a disk I have that has Win2000 on it. I booted to that disk on the XP machine hooked the NIC to the cable modem and connected to the Internet without nary a problem, ipconfig gave me IP address's.
Ok so the issue is with XP not the devices
I don't want to do a System Restore too many program registry settings will be lost and I don't want to spend many hours reinstalling the programs.
A Repair may work but not willing to go there just yet cause I figure this issue probably has an actual fix. I ran the network diagnoses as I stated in that other question and I am no longer getting the following so the fresh installed cured that problem.
===================
- Internet Explorer Web Proxy WMI Error FAILED
Unable to connect to WMI namespace 'netdiagnostics'
Computer Information
- Computer System WMI Error FAILED
Unable to connect to WMI namespace 'win32_computersystem'
- Operating System WMI Error FAILED
Unable to connect to WMI namespace 'win32_operatingsystem'
- Version WMI Error FAILED
Unable to connect to WMI namespace 'win32_operatingsystem'
Modems and Network Adapters
- Modems WMI Error FAILED
Unable to connect to WMI namespace 'win32_potsmodem'
- Network Adapters WMI Error FAILED
Unable to connect to WMI namespace 'win32_networkadapterconfi
- Network Clients WMI Error FAILED
Unable to connect to WMI namespace 'win32_networkclient'
===================
did this thow an error 7003 into the event log?
ASKER
FE networking isn't something a I know a lot about especially when problems arise.
chicagoan no envent logs associated with the problem.
chicagoan no envent logs associated with the problem.
Have you tried running the MS netdiag tool? (This command-line diagnostic tool helps to isolate networking and connectivity problems by performing a series of tests to determine the state of your network client and whether it is functional.)
http://download.microsoft.com/download/win2000platform/netdiag/1.00.0.1/nt5/en-us/NetDiag_setup.exe
http://download.microsoft.com/download/win2000platform/netdiag/1.00.0.1/nt5/en-us/NetDiag_setup.exe
Come to think of it, this will not work if we are not getting an IP. hmmmm
The NIC has a valid MAC? (seen some shipped with bogus macs lately)
Tried setting the nic to 10Mb 1/2 duplex explicitly?
Tried removing all the networking components in safe mode, rebooting to refresh the IP stack?
U sure XP detected the right thing and installed the right driver?
Tried setting the nic to 10Mb 1/2 duplex explicitly?
Tried removing all the networking components in safe mode, rebooting to refresh the IP stack?
U sure XP detected the right thing and installed the right driver?
Hey Spence!! First Happy Holidays to you and yours!!
now have you tried this
remove the Winsock and Winsock2 key from the registry HKLM-System-CurrentControl
After the reboot, go into the Network Connection Properties, selected install, —> "Have Disk", point it to the %SYSTEMROOT%/inf/nettcpip.
now have you tried this
remove the Winsock and Winsock2 key from the registry HKLM-System-CurrentControl
After the reboot, go into the Network Connection Properties, selected install, —> "Have Disk", point it to the %SYSTEMROOT%/inf/nettcpip.
checked that DHCP service is running?
ASKER
chicagoan I don't think it is a MAC problem since the NIC works when I boot to the disk with Win2000 and the connection works from there.
>>>U sure XP detected the right thing and installed the right driver?
Yeah It isn't a driver problem because I tried a different card same results.
I have been playing around with System Restore and have found some restore points that the networking works. This is a pain in the butt because the SR takes about 45 mins to do its thing. So I think this may be a registry setting that is the cause but I don't know what settings could be involved.
>>>U sure XP detected the right thing and installed the right driver?
Yeah It isn't a driver problem because I tried a different card same results.
I have been playing around with System Restore and have found some restore points that the networking works. This is a pain in the butt because the SR takes about 45 mins to do its thing. So I think this may be a registry setting that is the cause but I don't know what settings could be involved.
ASKER
Hi Steve and a First Happy Holidays to you and yours right back at you.
Umm I don't think the winsock is the problem either because I can connect to the Internet using my DSL card and/or modem. Although correct me if I am wrong if one can connect to the net then wouldn't the winsock be Ok.
Umm I don't think the winsock is the problem either because I can connect to the Internet using my DSL card and/or modem. Although correct me if I am wrong if one can connect to the net then wouldn't the winsock be Ok.
ASKER
>>>checked that DHCP service is running?
Doesn't seem to matter if it is running or not. I should have warned you all this probably wouldn't be an easy fix. Most questions I ask here at EE don't end up with solutions. :)
Doesn't seem to matter if it is running or not. I should have warned you all this probably wouldn't be an easy fix. Most questions I ask here at EE don't end up with solutions. :)
Yes, but what better place to ask them....
Continuing to monitor and hoping the answer comes... :)
FE
Continuing to monitor and hoping the answer comes... :)
FE
>>Umm I don't think the winsock is the problem either because I can connect to the Internet using my DSL card and/or modem
You are probably right. no firewalls right?
You are probably right. no firewalls right?
ASKER
Zone Alarm but the restore point I am at now also has Zone Alarm and the network is woriking and I am posting this comment using the cable modem. Now after this restore point is when I installed VMware. Anybody know if VMware with its bridged networking protocols could be a problem. Although I have disabled them before but the problem remained.
Just wanted you all to know, that while I was watching for answers to come in, I realized that my laptops Logical Disk Manager was not cycling and could not start. Forget the troubleshooting... delete the partition and start over I say! Guess we will be staying up to watch for Santa tonight.
If anyone sees him let me know so I can be ready for him this year!
FE
If anyone sees him let me know so I can be ready for him this year!
FE
ASKER
:)
why don't you try this , go to your n/w adapter configutation and try to set linkspeed and duplex manually to a lower speed , try different values , matching on both your m/c .
Hi
U did not mention how u connect the 2 computers. Are they connected via switch (hub) or crossed cable? If u are sharing the internet connection then u would need a router or 2 network cards, one for the ethernet cable modem and one for the other computer.
Pls advise
tekcentre
U did not mention how u connect the 2 computers. Are they connected via switch (hub) or crossed cable? If u are sharing the internet connection then u would need a router or 2 network cards, one for the ethernet cable modem and one for the other computer.
Pls advise
tekcentre
Man, what a pain!
Have you tried removing the drivers for your NW card, restarting, and letting windows networking wizard try to connect you? If you connect with a router or switch, or another computer via crossover cable, can you communicate through your network card?
TNC
Have you tried removing the drivers for your NW card, restarting, and letting windows networking wizard try to connect you? If you connect with a router or switch, or another computer via crossover cable, can you communicate through your network card?
TNC
You mention that the restore point that works was before installing VMWare. Did it start to fail immediately after installing VMWare, or at another time? In other words, have you narrowed down the problem inception to the install of VMWare?
Do you let Microsoft throw updates onto your machine whenever they want, or do you selectively perform your Windows Update process?
Do you let Microsoft throw updates onto your machine whenever they want, or do you selectively perform your Windows Update process?
ASKER
Ok I got impatient and just stayed with that Restore point and just bit the bullet and reinstalled the programs from that point on. Now after every install of software including VMware I checked that at least the cable modem was still connecting to the Internet. And I haven't lost that connection.
Now here we take twist, for a while I could get both this machine and the Win2000 machine to acknowledge that the each of the two where members of the work group. However neither machine would allow the other to connect to it in any form. Throwing messages like "Network path not found" and "you might not have permission to use this network resource". And no there are no naming conflicts as Microsoft suggests might be the problem. ICS is not checked on any of the devices. I have removed all the protocols and the NIC drivers on the Win2000 machine and reconfigured them. Now the computers don't even acknowledge that other exists.
Cable modem is still connecting to the Internet which out of the two (networking vs Internet connection) is by far the more important of the two. The lost of the networking isn't an urgent thing but the Internet on was. I also borrowed, just for testing this problem, a friends Windows 2003 CD and installed it on its own disk in the XP machine.. Mainly to see if this was an XP issue or not. Well the same problem is present in the Win2003 test disk. At first it threw those errors and then now doesn't even acknowledge that the WIn2000 machine is part of the work group and vica-versa. Cable modem works though so now I am more stumped then when I started but am glad that I am no longer getting 0's as IP addresses.
Now here we take twist, for a while I could get both this machine and the Win2000 machine to acknowledge that the each of the two where members of the work group. However neither machine would allow the other to connect to it in any form. Throwing messages like "Network path not found" and "you might not have permission to use this network resource". And no there are no naming conflicts as Microsoft suggests might be the problem. ICS is not checked on any of the devices. I have removed all the protocols and the NIC drivers on the Win2000 machine and reconfigured them. Now the computers don't even acknowledge that other exists.
Cable modem is still connecting to the Internet which out of the two (networking vs Internet connection) is by far the more important of the two. The lost of the networking isn't an urgent thing but the Internet on was. I also borrowed, just for testing this problem, a friends Windows 2003 CD and installed it on its own disk in the XP machine.. Mainly to see if this was an XP issue or not. Well the same problem is present in the Win2003 test disk. At first it threw those errors and then now doesn't even acknowledge that the WIn2000 machine is part of the work group and vica-versa. Cable modem works though so now I am more stumped then when I started but am glad that I am no longer getting 0's as IP addresses.
ASKER
Oh and there are no routers or hubs involved here. Just a straight connection with a CAT 5 cable strung between the two machines. the Odd thing is that the networking at one timed worked and then we were gone for a few days an durning that time we had both machines turned off. Interestingly enough when got home and turned the machines back on the networking was lost. the other odd thing is that the NIC's in both machine will work to connect to the Internet when I connect each one at a time to the cable modem.
Sounds like we need an Exorcist here...
>>Just a straight connection with a CAT 5 cable strung between the two machines
You of course mean a crossover cable
You of course mean a crossover cable
ASKER
>>>you might not have permission to use this network resource
Yeah :)
Yeah :)
ASKER
FE if you know of a good Exorcist send them my way. :)
Hi again,
Can u check your cable with a cable tester, or change your cable (must be a crossed cable) and try? If your cable modem is ethernet, then u will need two NICs as explained above. If you can connect to the internet with your cable modem in one machine and if u have 2 NICs in that same machine, then probably is a cable problem between the 2 NICs of the 2 computers. About the win2k machine, is there a login name and password with administrative rights? If so try using the same login and password when prompted. OR try typing "administrator" with no password. The other option is to create a new Administrator account in the win2k machine with password and then try again with new login name and password on the other machine when prompted.
tekcentre
Can u check your cable with a cable tester, or change your cable (must be a crossed cable) and try? If your cable modem is ethernet, then u will need two NICs as explained above. If you can connect to the internet with your cable modem in one machine and if u have 2 NICs in that same machine, then probably is a cable problem between the 2 NICs of the 2 computers. About the win2k machine, is there a login name and password with administrative rights? If so try using the same login and password when prompted. OR try typing "administrator" with no password. The other option is to create a new Administrator account in the win2k machine with password and then try again with new login name and password on the other machine when prompted.
tekcentre
Are you only binding IP to the NICs or are you trying to use any other protocols?
Just for kicks (means if it doesn't work, kick it) try NetBEUI on your inter-computer link, or NetBIOS over IPX, just to narrow it down a bit. If your inter-computer link works with both NetBEUI and IPX, then it's something wrong with your IP configuration. If it doesn't work with either, you should suspect hardware or drivers.
Just for kicks (means if it doesn't work, kick it) try NetBEUI on your inter-computer link, or NetBIOS over IPX, just to narrow it down a bit. If your inter-computer link works with both NetBEUI and IPX, then it's something wrong with your IP configuration. If it doesn't work with either, you should suspect hardware or drivers.
ASKER
I will try what you suggest ShineOn but I am already leaning towards a possible faulty Cross Over adapter. I know all the NIC's work and the two cables I have hooked to the NIC's because when I have connected them to the cable modem I can connect to the Internet without a problem. And the connection to the cable modem does not use the Cross Over adapter. The Cross Over adapter is the only thing that is different between connecting to the Internet and the network. And couple that with fact that the network did work at one time an then quit working and reinstalling the NIC's drivers and the same with the network Protocols, Clients, Services and not to mention testing all this on different OS's seems to indicate to me that the issue almost has to be a problem with the equipment and in this case the Cross Over adapter. At least I hope I have narrowed it down to that being the problem. Got to wait until I get another adapter to test with which probably won't happen for a couple of days.
You do mean "crossover cable" - not "crossover adapter" - right?
ASKER
Actually it is a crossover adapter hooked at the end of the cable. Been using it for a couple of years with no problem until recently. On the adapter it says IEC Crossover Adapter.
Ah, I see.
I usually just make a crossover cable, myself. 'Course to do that, you need a crimper and RJ45 ends... ;)
I usually just make a crossover cable, myself. 'Course to do that, you need a crimper and RJ45 ends... ;)
ASKER
:)
Could this be a distance issue? or imporperly created cable? I have found that if you dont use the correct twisted pairs or the distance is to great that communications are sporadic at best, and if the run is kinda long the crossover adapter might not be helping with the signal strength. But some of the things you say make me think that it couldnt be hardware, like that fact that win2000 disk ran the network fine.
ASKER
Well it is similar to this problem
https://www.experts-exchange.com/questions/20847982/the-list-of-servers-for-this-workgroup-is-not-currently-available.html
And I have tried every thing suggested there and host of other things that have been suggested in other questions with the similar or same problem. No luck. And I have scoured the Web. Lots of people with this problem for most no solution. For a problem the seems to be semi-common it is more then just a little aggravating that the problem seems unsolvable.
https://www.experts-exchange.com/questions/20847982/the-list-of-servers-for-this-workgroup-is-not-currently-available.html
And I have tried every thing suggested there and host of other things that have been suggested in other questions with the similar or same problem. No luck. And I have scoured the Web. Lots of people with this problem for most no solution. For a problem the seems to be semi-common it is more then just a little aggravating that the problem seems unsolvable.
SO what happened when u changed the crossover adapter?
tekcentre
tekcentre
Have you tried turning on any other protocols yet, to narrow it down a bit, like I suggested? If they "see" each other using NetBEUI or NetBIOS over IPX that would narrow it down to something IP-specific and eliminate hardware issues as the cause.
ASKER
ShineOn quite frankly I don't know if I have or not. I have tried a lot of things and have noticed a lot of posts on the WEB of people with the same problem and the problem in many cases goes unresolved.
>>>SO what happened when u changed the crossover adapter?
I tried a HUB, and nothing changed.
Well I tell you I can ping sometimes from machine "A" to machine "B's" IP address with no errors, but throws the errors I have posted when trying to get to machine "B" through the Network Neighborhood and vica vers. But machine "B" errors when pinging the IP address on machine "A" most of the time. "A" and "B" usually acknowledges the other is there but that is as far as it goes. I have tried three different OS's on just one machine ("A"). I have changed NIC's and cables the results are the same. I am going try a parallel install on the Win2000 machine ("B") to see if maybe the current Win2000 is somehow the problem. Although like I said the network was working fine then after shutting the two machines down for 3 of four days while we were out town then turning them back on the network vanished.
My third machine, which I mothballed as a spare machine a few months ago, when I took it out of storage has crapped out on me so until I can get around to fixing it I can't use it to test if it is one particular machine that is the problem or not.
It is just plain weird just like that WMI problem I had https://www.experts-exchange.com/questions/20802031/WMI-problem.html
Lots of people with the same problem that still has of yet found an answer to fix the problem other than a fresh install. A Repair install doesn't even fix that problem.
Like I said when I run into a problem I tend to have ones that there seems to be no real working solutions too. :(
>>>SO what happened when u changed the crossover adapter?
I tried a HUB, and nothing changed.
Well I tell you I can ping sometimes from machine "A" to machine "B's" IP address with no errors, but throws the errors I have posted when trying to get to machine "B" through the Network Neighborhood and vica vers. But machine "B" errors when pinging the IP address on machine "A" most of the time. "A" and "B" usually acknowledges the other is there but that is as far as it goes. I have tried three different OS's on just one machine ("A"). I have changed NIC's and cables the results are the same. I am going try a parallel install on the Win2000 machine ("B") to see if maybe the current Win2000 is somehow the problem. Although like I said the network was working fine then after shutting the two machines down for 3 of four days while we were out town then turning them back on the network vanished.
My third machine, which I mothballed as a spare machine a few months ago, when I took it out of storage has crapped out on me so until I can get around to fixing it I can't use it to test if it is one particular machine that is the problem or not.
It is just plain weird just like that WMI problem I had https://www.experts-exchange.com/questions/20802031/WMI-problem.html
Lots of people with the same problem that still has of yet found an answer to fix the problem other than a fresh install. A Repair install doesn't even fix that problem.
Like I said when I run into a problem I tend to have ones that there seems to be no real working solutions too. :(
Hi
Microsoft networking has no problems if u follow protocols.
U said u were going to change the crossover adapter but that didn't happen but instead u used a hub. By the way is the hub a new one and what model? Have u tested the cables with a cable tester or changed to new cables?
tekcentre
Microsoft networking has no problems if u follow protocols.
U said u were going to change the crossover adapter but that didn't happen but instead u used a hub. By the way is the hub a new one and what model? Have u tested the cables with a cable tester or changed to new cables?
tekcentre
I be interested to see what a packer sniffer like ethereal sees going on.
By the way using a hub still does not solve your internet connection sharing problems, u need a router or 2 network cards on the computer that is sharing the internet connection.
tekcentre
tekcentre
oh tekcentre, my guess is the person that has the most expert points in all of ee would know that :).
theplen
u a friend of crazyone?
y the most expert points is not solving the problem?
tekcentre
u a friend of crazyone?
y the most expert points is not solving the problem?
tekcentre
:)
Just for kicks, try NetBIOS over IPX. If your network neighborhood/my network places view shows up and stays there consistently, then it can't be hardware, and it has to be an IP problem of some sort.
It would be too cool if we could solve this apparently unsolvable problem that seems to be happening all over the place, don't you think?
It would be too cool if we could solve this apparently unsolvable problem that seems to be happening all over the place, don't you think?
ASKER
ShineOn my intention was/is to try that just in case I didn't do it earlier. :)
Maybe today or later this week.
folks if you read my earlier post you will note that I have two NIC's on machine "A". One is connected to the cable modem. I tested both NIC's ability to connect through the cable modem to the Internet and neither NIC has a problem doing that. So at least we know that the TCP/IP protocol running through these NIC's work, apparently any way. I have all the Protocols setup precisely the way that not only MS recommends but also what the Network Guru's recommend. The HUB was just to experiment with to find out if the problem was with the crossover adapter. Using the HUB produced the same errors so I returned the HUB from where I got it from. And don't forget the key thing here, "The networking worked fine for quite a while and then vanished, Poof it was no longer there and no changes had been made to either machine between the time that it was working and when it stopped working."
Also at this point ICS is not my focus. The focus is why can't these two machines that do now most of the time acknowledge that the other is there throw error messages when trying to actually gain entry to the other. Like why when I go into the Network Neighborhood and I click on the machine name of the other computer I get at times "Network path not found". Now if you think about it how could the Network path not be found since the machine is being listed in the workgroup. If the path couldn't be found then how could the machine get listed. Weird.
>>>It would be too cool if we could solve this apparently unsolvable problem that seems to be happening all over the place, don't you think?
Yep it sure would :)
Maybe today or later this week.
folks if you read my earlier post you will note that I have two NIC's on machine "A". One is connected to the cable modem. I tested both NIC's ability to connect through the cable modem to the Internet and neither NIC has a problem doing that. So at least we know that the TCP/IP protocol running through these NIC's work, apparently any way. I have all the Protocols setup precisely the way that not only MS recommends but also what the Network Guru's recommend. The HUB was just to experiment with to find out if the problem was with the crossover adapter. Using the HUB produced the same errors so I returned the HUB from where I got it from. And don't forget the key thing here, "The networking worked fine for quite a while and then vanished, Poof it was no longer there and no changes had been made to either machine between the time that it was working and when it stopped working."
Also at this point ICS is not my focus. The focus is why can't these two machines that do now most of the time acknowledge that the other is there throw error messages when trying to actually gain entry to the other. Like why when I go into the Network Neighborhood and I click on the machine name of the other computer I get at times "Network path not found". Now if you think about it how could the Network path not be found since the machine is being listed in the workgroup. If the path couldn't be found then how could the machine get listed. Weird.
>>>It would be too cool if we could solve this apparently unsolvable problem that seems to be happening all over the place, don't you think?
Yep it sure would :)
ASKER
Well I did the NetBIOS over IPX and the NetBEUI and when doing ipconfig the IP address came back all 0's. So I removed those protocols and now I can't get paste the all 0's IP address so I am back where I started. :(
Spence, just for fun fix the winsock (it couldn't hurt, and may help)
ASKER
Hi Steve have you been able to golf any in the snow? :)
Actually I did do the winsock fix a couple of times. Sorry I forgot to mention that.
And just know I did an IPCONFIG /all and got an IP address on the LAN NIC. But I am not getting the other machine "B" to get listed in the Network Neighborhood.
BTW the internet connection NIC hasn't dropped any connection at any time so it just has to do with the two machines not being able to get them to let the other access it.
Actually I did do the winsock fix a couple of times. Sorry I forgot to mention that.
And just know I did an IPCONFIG /all and got an IP address on the LAN NIC. But I am not getting the other machine "B" to get listed in the Network Neighborhood.
BTW the internet connection NIC hasn't dropped any connection at any time so it just has to do with the two machines not being able to get them to let the other access it.
>>Hi Steve have you been able to golf any in the snow?
LOL, not when it's 10 above ( I golf in the 70's, when it gets colder than that I won't play *grin*
what happens if you type net view from a command prompt (on each box)
LOL, not when it's 10 above ( I golf in the 70's, when it gets colder than that I won't play *grin*
what happens if you type net view from a command prompt (on each box)
ASKER
>>>net view
For now I just get the only the machine name on machne "A" and nothing on machine "B". But both machines have IP addresses.
For now I just get the only the machine name on machne "A" and nothing on machine "B". But both machines have IP addresses.
Okay. I'm no expert on networking...need to work on this....but I wonder if the reason you can see the internet, but not your other machine through your crossover cable is because the IP routing table is only capable of using one gateway?
I once had a user who would occasionally call because she could not get on the internet or print documents on our local domain. I struggled with this problem for several weeks until one day I was reading about IP routing tables and found that if the RIP listener was activated on a machine it would go to the nearest gateway which was not the gateway to our WAN and the Internet. It was to another older subsystem we have. I disabled this users RIP listener and I haven't heard a peep out of her since.
In your case I wonder if you would benefit from activating the RIP listener? Or the Routing and Remote Access Service?
I once had a user who would occasionally call because she could not get on the internet or print documents on our local domain. I struggled with this problem for several weeks until one day I was reading about IP routing tables and found that if the RIP listener was activated on a machine it would go to the nearest gateway which was not the gateway to our WAN and the Internet. It was to another older subsystem we have. I disabled this users RIP listener and I haven't heard a peep out of her since.
In your case I wonder if you would benefit from activating the RIP listener? Or the Routing and Remote Access Service?
Are you still working on this? A real brain tease, eh? :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
>>>When you had NetBIOS over IPX running, were your 2 PCs able to "see" each other?
Nope :(
Nope :(
Hi
Have u tried this solution.
On MachineA BIND the 2 network cards using windows "Create a home network environment" wizard. Then the IP address should be 192.168.0.1, which is also your gateway address.
Then on the other machine do the same thing OR
Assign an IP address of 192.168.0.2 manually
Restart MachineA first and then the other machine.
tekcentre
Have u tried this solution.
On MachineA BIND the 2 network cards using windows "Create a home network environment" wizard. Then the IP address should be 192.168.0.1, which is also your gateway address.
Then on the other machine do the same thing OR
Assign an IP address of 192.168.0.2 manually
Restart MachineA first and then the other machine.
tekcentre
ASKER
ShineOn what I meant to say is they were seeing each other before without IPX or NetBEUI but when I tried these protocols the machines did not see each other at all. And after removing them the machines still don't see each other now.
tekcentre I tried static IP address's a long time ago and of and I keep trying to use them for testing purposes. When the machines were seeing each other use static address's produced the same results.
tekcentre I tried static IP address's a long time ago and of and I keep trying to use them for testing purposes. When the machines were seeing each other use static address's produced the same results.
Well. Hmmm.
If you can't get your PCs to "see" each other using another protocol, I hesitate to point fingers at IP.
If you have verified that the cables are good and that the hub or crossover adapter is good, and have tried different NICs, then it goes much deeper than IP or hardware.
In my opinion you have accurately defined the probable cause of the problem in your question, so we all should stop putzing with IP, hardware, protocols, etc. and try to figure out what is wrong with your XP system that is causing this issue.
Fair statement?
If you can't get your PCs to "see" each other using another protocol, I hesitate to point fingers at IP.
If you have verified that the cables are good and that the hub or crossover adapter is good, and have tried different NICs, then it goes much deeper than IP or hardware.
In my opinion you have accurately defined the probable cause of the problem in your question, so we all should stop putzing with IP, hardware, protocols, etc. and try to figure out what is wrong with your XP system that is causing this issue.
Fair statement?
ASKER
ShineON I will be damned but I just tried the IPX thing again and not only can the computers see each other I can now access them. So what does that tell us?
It tells us that troubleshooting Windows problems is not an exact science.
All together now!
1..
2..
3..
Gaaah!
All together now!
1..
2..
3..
Gaaah!
ASKER
LOL
Why don't you post the IPX thing here https://www.experts-exchange.com/questions/20847982/the-list-of-servers-for-this-workgroup-is-not-currently-available.html maybe it might help that individual and then we can pronounce you the Network super hero. :)
Why don't you post the IPX thing here https://www.experts-exchange.com/questions/20847982/the-list-of-servers-for-this-workgroup-is-not-currently-available.html maybe it might help that individual and then we can pronounce you the Network super hero. :)
Sorry, Spence, but I gotta go to bed, and I probably won't be back to EE until tomorrow night (it is night here - actually, 5 minutes into the AM.)
What to do, what to do? I don't want to stay awake thinking about it, so... ;)
What to do, what to do? I don't want to stay awake thinking about it, so... ;)
ASKER
Well ShineOn you definetly earned the candy for this question. I appreciate everybodies help and maybe later we can figure out why using IPX resovled the issue. But for now I ain't messing with something that now works so IPX stays in place for me. :)
IPX is a better transport for NetBIOS than IP is. NetBIOS over IP tends to be flaky on-and-off, in no small part because IPX broadcasts service advertisements using SAP, which is why it's known to be "chatty." IP does not broadcast service advertisements, and the standard IP protocol for service location, SLP, is not used by Windows networking. Windows networking, when in a peer or legacy domain environment, requires LMHOSTS or WINS for name resolution, otherwise it's catch-as-catch-can. Active Directory uses DNS for name resolution, which means you either have to have a DNS server that has all of the services' addresses and names, or you have to populate your HOSTS files with appropriate name entries.
You could try putting all of your host names in LMHOSTS in the appropriate LMHOSTS format, make sure that IP is set to use LMHOSTS, and turn off IPX, to see if that fixes your IP problem.
You could try putting all of your host names in LMHOSTS in the appropriate LMHOSTS format, make sure that IP is set to use LMHOSTS, and turn off IPX, to see if that fixes your IP problem.
Since I work very little with IPX, this is a great thing to know.
Thanks ShineOn for the excellent explanation....
FE
Thanks ShineOn for the excellent explanation....
FE
Hi
What I wanted to know is whether MachineA has a network bridge. (binding the 2 network adapters together).?
Thanks
tekcentre
What I wanted to know is whether MachineA has a network bridge. (binding the 2 network adapters together).?
Thanks
tekcentre
Out of curiosity (and this is a long read) when you http to your cable modem what level of firewall do you have? (low medium and blah blah?)
ooh and one other thing - (i just read this entire thread) did you also ipconfig /release and ipconfig /renew?
hi
this question was asked on Dec 24, 2003.
today is Aug 24th, 2004
i think the moderator should decide on this question
this is too long in my opinion
this question was asked on Dec 24, 2003.
today is Aug 24th, 2004
i think the moderator should decide on this question
this is too long in my opinion
tekcentre, the long-thread question has been accepted, the answer is http://10161636 from ShineOn.
RobertMAtkins, the question owner is CO, the most crazy guy and the top dog of EE, i believe he had tried to release and renew ipconfig before his posting. hehe. :)
regards,
bbao
RobertMAtkins, the question owner is CO, the most crazy guy and the top dog of EE, i believe he had tried to release and renew ipconfig before his posting. hehe. :)
regards,
bbao
I have seen a lot longer threads that even though closed, seem to just keep attracting comments... :)
What is funny though, is the 0 ip's. It must be seeing the DHCP and retrieving those address blocks, or it would return an APIPA address.
I just want to know one thing. Where can I get one of those W2K roms?
FE