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)
Any ideas/help?
Graham
What did you name the domain on the PDC when you installed server? Are you
trying to logon to the correct domain?
Graham <grah...@virgin.net> wrote in message
news:LAIG5.8092$NQ4.1...@news2-win.server.ntlworld.com...
Have you added the workstation to the domain?
Created any shares on either machine? (the default shares are hidden)
If the drives on the workstation are shared, try mapping one from
<start><run>\\server_name\share_name and see if you get a drive mapping...
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.
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...
Best of luck w/ the problem and the test.
Allan
MCP + I, MCSE
Still, this has taught me a lot, more than reading the book.
Many thanks to all...
Grahame
Allan H Spissinger <all...@home.com> wrote in message
news:poNG5.470864$8u4.5...@news1.rdc1.bc.home.com...
A very small time saver, but each one helps...
Allan
MCP + I, MCSE
"Graham" <grah...@virgin.net> wrote in message
news:R80H5.9877$NQ4.2...@news2-win.server.ntlworld.com...