I have a PC with NT Server as PDC and Client with NT Workstation. Neither computer can see each other. I cannot create accounts on my server from my client, I cannot "see" my server in my client Explorer (or vice versa). To all intents and purposes, each PC is invisible to each other.
I am using TCP/IP, but not DHCP with manually set IP addresses. I can successfully ping each other and know that the link is working, but apart from that, I cannot do anything with it.
I suspect I have done something amiss, as I want a create a number of user accounts on my server which I can log into from my client in order to play with. (MCSE Enterprise exam looming)
> I have a PC with NT Server as PDC and Client with NT Workstation. Neither > computer can see each other. I cannot create accounts on my server from my > client, I cannot "see" my server in my client Explorer (or vice versa). To > all intents and purposes, each PC is invisible to each other.
> I am using TCP/IP, but not DHCP with manually set IP addresses. I can > successfully ping each other and know that the link is working, but apart > from that, I cannot do anything with it.
> I suspect I have done something amiss, as I want a create a number of user > accounts on my server which I can log into from my client in order to play > with. (MCSE Enterprise exam looming)
> I have a PC with NT Server as PDC and Client with NT Workstation. Neither > computer can see each other. I cannot create accounts on my server from my > client, I cannot "see" my server in my client Explorer (or vice versa). To > all intents and purposes, each PC is invisible to each other.
> I am using TCP/IP, but not DHCP with manually set IP addresses. I can > successfully ping each other and know that the link is working, but apart > from that, I cannot do anything with it.
> I suspect I have done something amiss, as I want a create a number of user > accounts on my server which I can log into from my client in order to play > with. (MCSE Enterprise exam looming)
The connection between both of your computers is a standard peer to peer network?
Possible - Have a look at your Server Service and make sure that it is running. Also have a look at your Browser Service and make sure that it is running.
Also try doing a search computer and look up the IP address of the other computer and see if you are able to find it that way.
Let me know what you find out. I have some other ideas but they might be getting a bit complicated then.
> I have a PC with NT Server as PDC and Client with NT Workstation. Neither > computer can see each other. I cannot create accounts on my server from my > client, I cannot "see" my server in my client Explorer (or vice versa). To > all intents and purposes, each PC is invisible to each other.
> I am using TCP/IP, but not DHCP with manually set IP addresses. I can > successfully ping each other and know that the link is working, but apart > from that, I cannot do anything with it.
> I suspect I have done something amiss, as I want a create a number of user > accounts on my server which I can log into from my client in order to play > with. (MCSE Enterprise exam looming)
I had a similar/same problem extensively with my 2 machines, 1 NT4 server (PDC) and a Win98 workstation.
Neither machine would see the other. Didn't matter the shares etc. Proved that the connection worked via PING, etc. Got connections via NetBEUI, IPX, and DID connect via TCP but STILL wouldn't see the other in network neighborhood, even after drives were mapped.
IF, I searched for computer by name via network neighborhood, then it saw it, and then the NN/Explorer worked just fine. If I didn't, then nothing--yet the connections work via IP address, or the other protocols.
In my case I determined that it was the Browse List. If I waited, I believe it was pretty much 30-60 minutes, then it would become visible in NN. Previously I had been rebooting too often doing trouble shooting, or using the "search for computer" option to get it visible right away.
In your case:
- Is you NT Workstation set to be part of the domain? - Are you logging on as the Administrator? - Is a machine account setup on the PDC for the WS? - Have you altered the USER RIGHTS to prevent network access? - Do you have WINS setup and tried mapping a drive via NetBIOS name? (This will also let you see if the WS is registering itself to WINS, in the WINS manager) - Have you tried connecting via another Protocol (NetBEUI for easy connect)? - Have you checked the Bindings to see if Server and protocols are bound to the NIC(s)? (although if you can PING it they should be bound...)
Hmmm, that's all I can think of right now. Maybe if you provide more details...
> I have a PC with NT Server as PDC and Client with NT Workstation. Neither > computer can see each other. I cannot create accounts on my server from my > client, I cannot "see" my server in my client Explorer (or vice versa). To > all intents and purposes, each PC is invisible to each other.
> I am using TCP/IP, but not DHCP with manually set IP addresses. I can > successfully ping each other and know that the link is working, but apart > from that, I cannot do anything with it.
> I suspect I have done something amiss, as I want a create a number of user > accounts on my server which I can log into from my client in order to play > with. (MCSE Enterprise exam looming)
Yep. Sorted. An obscure tiny small paragraph in my Exam Cram mentioned that I have to use Server Manager to add my workstation to my domain. D'oh! (I did have a bit of a name conflict as well).
Still, this has taught me a lot, more than reading the book.
> I had a similar/same problem extensively with my 2 machines, 1 NT4 server > (PDC) and a Win98 workstation.
> Neither machine would see the other. Didn't matter the shares etc. Proved > that the connection worked via PING, etc. Got connections via NetBEUI, IPX, > and DID connect via TCP but STILL wouldn't see the other in network > neighborhood, even after drives were mapped.
> IF, I searched for computer by name via network neighborhood, then it saw > it, and then the NN/Explorer worked just fine. If I didn't, then > nothing--yet the connections work via IP address, or the other protocols.
> In my case I determined that it was the Browse List. If I waited, I believe > it was pretty much 30-60 minutes, then it would become visible in NN. > Previously I had been rebooting too often doing trouble shooting, or using > the "search for computer" option to get it visible right away.
> In your case:
> - Is you NT Workstation set to be part of the domain? > - Are you logging on as the Administrator? > - Is a machine account setup on the PDC for the WS? > - Have you altered the USER RIGHTS to prevent network access? > - Do you have WINS setup and tried mapping a drive via NetBIOS name? > (This will also let you see if the WS is registering itself to WINS, in > the WINS manager) > - Have you tried connecting via another Protocol (NetBEUI for easy connect)? > - Have you checked the Bindings to see if Server and protocols are bound to > the NIC(s)? (although if you can PING it they should be bound...)
> Hmmm, that's all I can think of right now. Maybe if you provide more > details...
> > I have a PC with NT Server as PDC and Client with NT Workstation. Neither > > computer can see each other. I cannot create accounts on my server from my > > client, I cannot "see" my server in my client Explorer (or vice versa). To > > all intents and purposes, each PC is invisible to each other.
> > I am using TCP/IP, but not DHCP with manually set IP addresses. I can > > successfully ping each other and know that the link is working, but apart > > from that, I cannot do anything with it.
> > I suspect I have done something amiss, as I want a create a number of user > > accounts on my server which I can log into from my client in order to play > > with. (MCSE Enterprise exam looming)
Remember, if you log on as the Administrator (or equiv.) from the workstation it will automatically be registered so you don't have to manually add it in server manager.
> Yep. Sorted. An obscure tiny small paragraph in my Exam Cram mentioned that > I have to use Server Manager to add my workstation to my domain. D'oh! (I > did have a bit of a name conflict as well).
> Still, this has taught me a lot, more than reading the book.
