>>I have a peer to peer network using Windows Networking. Some of the systems are Windows95 some are Windows98. I am using TCP/IP protocal. The network as been working fine for quite some time. A new system has been added that was originally setup "offsite" connected to a WindowsNT 4.0 server, then the IP changed before the unit was shipped from the home office. Now we can not get the unit to "talk" to any of the other systems on the network. In the network neighborhood, it only see itself. The other systems see all the previously existing systems, but they do not see the new system. I've double checked all the settings and everything looks fine. The TCP/IP protocol seems to be working correclty, as I can ping it from the other workstations, and it accesses the internet and the remote E-Mail server with no problems.
>>
>>Any ideas and suggestions would be greatly apprecated!!!
>
>It sounds like the MS Networking Client is misconfigured; it's either set to attempt to log into a domain, or it's a member of the wrong Workgroup - peer-to-peer can't see other workgroups. The TCP/IP functionality seems to be working from your description, but the MS Networking is not; while you can ping it, you haven't stated if it is visible in Network Neighborhood from other systems; I assume that you're using NBT to provide NetBIOS functionality. You need to be in the same Workgroup, in the same subnet, and not set to log into a domain, since no authentication server is available and MS Networking would fail as a result. Ping, Internet gateways, POP3 and SMTP email protocols
>are not dependent on NetBIOS functionality.

Out of desperation I removed TCP/IP from all systems and replaced it with NetBEUI. After rebooting the system they all connected with no problem. Now that they were all browsing the network correctly, I replaced NetBEUI with TCP/IP and now all systems are working correctly. Thanks!