Tip: Run a free scan for common Windows errors ad

re: Question about 'Getting Network Neighborhood to recognize newly attached computers' Sunday, March 13, 2005 at 12:00 am Posted by JmC (14166 messages posted) Obviously something happened during the CDROM R&R. The first place to check is Device Manager. I suppose the drive could be conflicting with the LAN (NIC)? Networking Troubleshooting [Reply or follow-up to this message] re: Question about 'Getting Network Neighborhood to recognize newly attached computers' Sunday, March 20, 2005 at 5:47 pm Posted by Sdruid (76 messages posted) Could you elaborate on your question a bit... Describe your lan setup...computers, OS, switches, routers, etc....? what is R&R's a cdrom drive ? thanks... On Saturday, March 12, 2005 at 8:48 pm, Ron Wingfield wrote: >I have a question about Getting >Network Neighborhood to recognize newly attached computers: > >RE: The comment that if none of the suggestions work, then ". . .your network is >not configured correctly." Well, there is nothing wrong with my LAN. In fact, >this scenario used to work, only I R&R's a CDROM drive, . . .Windoze reconfigured >itself, and now the box in reference cannot be found by any other box on the LAN, >or vice versa. > > [Reply or follow-up to this message] re: Question about 'Getting Network Neighborhood to recognize newly attached computers' Monday, March 21, 2005 at 10:41 am Posted by Ron Wingfield (3 messages posted) ================================== Be glad to. I will describe the solution that I discovered and also suggest another bullet item for the suggestions provided by this article: "Getting Network Neighborhood to recognize newly attached computers" First, "R&R" is a common shop term for "Remove and Replace" or some combination of "remove, replace or repair". The two systems that I was trying to network at the time that I submitted my question were two similar Windows/98 boxes, one Compaq 1610 Presario Notebook, and the problem child was a Compaq 4508 DeskTop. Nothing sexy, but as I mentioned before, all was well prior to the R&R of the CDROM. The LAN is a small intranet connected via a Cayman 3220 Router, configured as a simple router, to which is attached is a Unix based server running FreeBSD v4.8, an HTTP server (Apache v2.0.28), DNS & BIND, et al. The HTTP server, which also runs several virtual hosts, requires a static IP address (so that the outside world can find it); therefore, all Windows workstations are assigned static IP addresses; consequently, DHCP cannot be used in the configurations. Finally, the router is connected to the internet via an ADSL wire.   The Solution. First, not until I temporarily gave up and proceeded with the installation of Windows/XP64 Beta on an Athlon 3400+ box, have I really understood the significance of the "Enter Password to Logon to Windows" prompt that always appears when starting up a Windows/98 system. I've always used a password, but never really appreciated the significance. (After all, . . .even if you just cancel the prompt, you can still access the internet via the LAN.) Note however, that Windows will not network with itself if you do not "Logon to Windows". In other words, the "Network Neighborhood" scenario will not find or acknowledge any Windows system that is not logged-on per the Windows "network scenario". The Windows documentation is less than enlightening on the subject. Also, as I struggled with the XP64 Beta installation (my first real use of any version of XP, I might add), I began to realize that the term or concept of "domain" means something different to the Windows culture than the rest of the TCP/IP world (why, I don't know, but that's for another argument). Regardless, I stumbled around, trying and always failing to successfully add my internet domain name to the Windows/XP64 networking scenario. The solution here was not to use the "domain" name. Why? . . .because I'm not running an intranet on a "Windoze" server. The problem that I was having with the Compaq desktop box involved some aspect of the installation or modification of the TCP/IP Network Protocol Component that must have occurred years ago (I have run CISCO VPN for Client, NetSoft Elite-Administrator and Affinity Systems 5250 Emulator for access to IBM OS/400 successfully on both the desktop and notebook). The only difference that I could ascertain between the desktop and notebook network configurations was that the TCP/IP component on the desktop system was displayed as shared, i.e., "TCP/IP (shared)". How this came to be, I have no idea. Everything, and I mean everything including R&R of the NIC indicated all functioning properly. I have never read in the online Windows documentation that the TCP/IP component can be "shared" or otherwise be displayed as shared. For that matter, shared with what? One would think that sharing of the TCP/IP component would be implicit with any host or client that needed it. Regardless, it occurred to me that I could delete the component and add it back. When I did so, everything works as advertised. Problem, but not the mystery, is solved. [Reply or follow-up to this message] re: Question about 'Getting Network Neighborhood to recognize newly attached computers' Monday, March 21, 2005 at 8:24 pm Posted by Sdruid (76 messages posted) Nice to hear... Glad somebody actually saw the "Logon to Windows" prompt in action or real-time and realizes that they just can't cancel out of it and keep on trucking....heheh. I get this all the time and I myself have had to troubleshoot it on my own Win98se machine which would actually disable and hide the "Logon to Windows" prompt after a windows reload. I found a registry key to change that puts everything back right. Remember that one people.....It almost drove me insane... When I ask people to explain the steps they took to get into windows and they say they just cancelled out of the logon - I have to explain to them what the logon really means and that cancelling out is not really an option if they want everything to work correctly. thanks... On Monday, March 21, 2005 at 10:41 am, Ron Wingfield wrote: > ================================== > Be glad to. I will describe the solution that I discovered and also suggest another >bullet item for the suggestions provided by this article: >"Getting >Network Neighborhood to recognize newly attached computers" > > First, "R&R" is a common shop term for "Remove and Replace" or some combination >of "remove, replace or repair". > > The two systems that I was trying to network at the time that I submitted my question >were two similar Windows/98 boxes, one Compaq 1610 Presario Notebook, and the problem >child was a Compaq 4508 DeskTop. Nothing sexy, but as I mentioned before, all was >well prior to the R&R of the CDROM. > > The LAN is a small intranet connected via a Cayman 3220 Router, configured as >a simple router, to which is attached is a Unix based server running FreeBSD v4.8, >an HTTP server (Apache v2.0.28), DNS & BIND, et al. The HTTP server, which also >runs several virtual hosts, requires a static IP address (so that the outside world >can find it); therefore, all Windows workstations are assigned static IP addresses; >consequently, DHCP cannot be used in the configurations. Finally, the router is >connected to the internet via an ADSL wire. > >   The Solution. > > First, not until I temporarily gave up and proceeded with the installation of >Windows/XP64 Beta on an Athlon 3400+ box, have I really understood the significance >of the "Enter Password to Logon to Windows" prompt that always appears when >starting up a Windows/98 system. I've always used a password, but never really appreciated >the significance. (After all, . . .even if you just cancel the prompt, you can still >access the internet via the LAN.) Note however, that Windows will not network with >itself if you do not "Logon to Windows". In other words, the "Network Neighborhood" >scenario will not find or acknowledge any Windows system that is not logged-on per >the Windows "network scenario". The Windows documentation is less than enlightening >on the subject. > > Also, as I struggled with the XP64 Beta installation (my first real use of any >version of XP, I might add), I began to realize that the term or concept of "domain" >means something different to the Windows culture than the rest of the TCP/IP world >(why, I don't know, but that's for another argument). Regardless, I stumbled around, >trying and always failing to successfully add my internet domain name to the Windows/XP64 >networking scenario. The solution here was not to use the "domain" name. Why? . >. .because I'm not running an intranet on a "Windoze" server. > > The problem that I was having with the Compaq desktop box involved some aspect >of the installation or modification of the TCP/IP Network Protocol Component that >must have occurred years ago (I have run CISCO VPN for Client, NetSoft Elite-Administrator >and Affinity Systems 5250 Emulator for access to IBM OS/400 successfully on both >the desktop and notebook). The only difference that I could ascertain between the >desktop and notebook network configurations was that the TCP/IP component on the >desktop system was displayed as shared, i.e., "TCP/IP (shared)". How this came to >be, I have no idea. Everything, and I mean everything including R&R of the NIC >indicated all functioning properly. I have never read in the online Windows documentation >that the TCP/IP component can be "shared" or otherwise be displayed as shared. For >that matter, shared with what? One would think that sharing of the TCP/IP component >would be implicit with any host or client that needed it. Regardless, it occurred >to me that I could delete the component and add it back. When I did so, everything >works as advertised. Problem, but not the mystery, is solved. [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows 98 Discussion Forum