Cannot Browse peer to peer network

[Mardawg]

I am attempting to set up a peer to peer network with 1 NT Workstation as a file server and a mixture of Windows95 and 98 machines.<br><br>The network cards are 3com 3c509b tx.<br>They are installed and seem to be working properly.<br><br>I am attempting to use TCP/IP as my protocol.<br><br>I have Checked and rechecked all of the network settings and I am unable to find any differences.&nbsp;&nbsp;The workgroup names are the same the ip addresses are sequential the subnet masks are all the same.<br><br>When I log on to a client machine I am able to ping every Ip address on the network. Including my own and the loopback.<br><br>Even so I am unable to open network neighborhood and see any of the client machines.&nbsp;&nbsp;I can not use the run command to open a network share either.&nbsp;&nbsp;I have tried different nics, and I have disabled tcp/ip and attempted to use NetBEUI all to no avail.<br><br>From a command prompt if I use the net view command I receive error 6118 the computers sharing resources on this network can not be reached.&nbsp;&nbsp;There is an article in tech net referencing a hot fix for this situation but even after I have applied the hot fix the same situation exists.<br><br><br>I am out of ideas and I need some help.<br>

 

[Mardawg]

Thanks Ripper it at least allows me to clarify further.<br><br>Everyone is a part of the same workgroup.&nbsp;&nbsp;File and print sharing is turned on.&nbsp;&nbsp;shares have been created for testing.&nbsp;&nbsp;Browse master has been disabled on the Windows9x machines(except for when I tested without the NT Workstation I set one machine as the browse master), and I am unsure of what the setting should be for LM Announce.<br><br>I am unsure of the NT Workstation login but I am thinking that that would not matter for the test of when I took it out of the picture and I am still unable to have a peer to peer with only the Windows9x machines.

 

[tmoses]

One thing that i have learned at school getting acess to dumb teachers who share their entire hard drives is how to do this.&nbsp;&nbsp;If you can find the ip address of the machine, you then need to find the NetBIOS name of the computer.&nbsp;&nbsp;That is the name that when you in control panel-&gt;network-&gt;identification-&gt;name-&gt;you set it there.&nbsp;&nbsp;IF you take the ip address and in a win95 or nt machine go to the command prompt and type nbtstat -A ipaddres, it will resolve the ip to netbios name.&nbsp;&nbsp;it will also give a list of diagnostic showing what the machine your looking at is running<br>ex.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NetBIOS Remote Machine Name Table<br><br>&nbsp;&nbsp;&nbsp;Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Status<br>---------------------------------------------<br>MICRON&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;00&gt;&nbsp;&nbsp;UNIQUE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Registered<br>WORKGROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;00&gt;&nbsp;&nbsp;GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Registered<br>MICRON&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;03&gt;&nbsp;&nbsp;UNIQUE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Registered<br>MICRON&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;20&gt;&nbsp;&nbsp;UNIQUE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Registered<br>WORKGROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;1E&gt;&nbsp;&nbsp;GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Registered<br><br>MAC Address = 44-45-53-54-00-00<br>the &lt;20&gt; means that it has sharing allowed and the &lt;ie&gt; shows what workgroup it is etc.. microsofts website has the entire technical readout if you want it...<br>The next step is to see if their are anyshares on it using<br>net view \\ipaddress or netbios name<br>after that you can just use net use as you said.&nbsp;&nbsp;As of how to set up the master domain controller in a win95 to nt workgroup i do not know.&nbsp;&nbsp;The only thing i could suggest and has worked for me is to try using a the netbios name if the ip does not work etc..&nbsp;&nbsp;But if the machines can see one another using nbtstat&nbsp;&nbsp;then they should be okay.&nbsp;&nbsp;If you get an error like must log in before completeing this operation, i think it has do making sure the nt box is the master domain controller ?&nbsp;&nbsp;The other thing if the ip address of the machines are 10.10.etc..&nbsp;&nbsp;i think windows does not like this because they are restricted to private networks.&nbsp;&nbsp;here is an article i found that coudl help you out, maybe <br><A HREF="

http://www.angelfire.com/md2/ackkatexts/texts/"

TARGET="_new">

http://www.angelfire.com/md2/ackkatexts/texts/</A><br>oh,

and if your going to do this for any important data , please make sure the users use strong passwords.&nbsp;&nbsp;Half the machines i have control of at school the teachers either used their names or no passwords at all. good luck<br><br> <p>moses<br><a href=mailto:tmoses@iname.com>tmoses@iname.com</a><br><a href=

http://home.cyberarmy.com/ackka>

my site</a><br>"In the beginning there was HTML, and it was good"<br>
by Nick Heinle, Designing with JavaScript<br>
<br>
<br>

 

[Mardawg]

I have an update to the issue the problem appears to be solved but I do not understand what happened.<br><br>Having exhausted every avenue I could come up with at the office I decided to try something a little different.<br><br>I set up a 2 node network at my house using the identical configuration as what I was using at the office.&nbsp;&nbsp;Once I got that working I took it all down and packed it up.&nbsp;&nbsp;I took the hub, the cables, and both computers into the office and set them up again at the office.&nbsp;&nbsp;Once I got them working I began to work the other computers into the new network and they worked.<br><br>Once I had them all working on this network I took the cables out of my hub and put thewm into the appropriate hub.&nbsp;&nbsp;THEY STILL WORKED!!!!!!!!!!&nbsp;&nbsp;Then I switched the cables from my cables to the office's cables.&nbsp;&nbsp;THEY STILL WORKED!!!!!!!!!!!!&nbsp;&nbsp;I took the two computers I brought from home out of the network and rebooted all of the remaining computers.&nbsp;&nbsp;THEY STILL WORKED!!!!!!!!!!<br><br>When I tried this latest experiment I made no changes to the existing computers and everything works now so as far as I am concerned the problem is solved but the mystery is much deeper.&nbsp;&nbsp;Anyone have any ideas?