Discussion Locked

Cant see network

0 helpful
18 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm having a problem with one workstation. This station is having a problem seeing the network , although the network can see it. The station can also access the internet so its obviously not the cabling. The server is NT4 and the workstation is NT4. What could this be please help

18 replies

by duskos

Check your WINS setting in Network, Properties, TCP/IP, Wins.

You can check your IP configuration from Command Prompt by running command:

ipconfig /all

You should see that your Node type is hybrid and the IP address of your WINS server.

You can go to Start menu, Find Computer and try to find the server from there.

by eltoncole

Good advice.

The node needs to be in the right domain. Just because it can hit the Internet (via MS Proxy Server?) doesn't mean all the domain config is correct.

Proxy could be allowing all access or troublesome node could be in trusting domain below proxy domain.

by eltoncole

Check to make sure you don't have a duplicate NetBios (machine) name.

Also check for duplicate SID if you used an image to stage the machine. Use a SID changer when ghosting NT Wkstn.

by eltoncole

The node should match (except for IP address) the nodes adjacent to it in configuration.

Possible exception: some nodes are, for net admin use or other specifid use, configured differently. I may have a node using a different subnet, defgateway, etc.

Using "Find Computer" is, however, just a different method to browse the network. If the node can't see the network in Network Neighborhood, it is extremely unlikley that Find Computers will give better results.

I've always found the "net view" and "net use" commands to be great for troubleshooting browse problems. When you issue "net view servername" you go directly to the server and query it, bypassing the browsers.

by eltoncole

I really don't think this is the problem.

ZoneAlarm, like all personal/desktop firewalls, guards against incoming connections. This node is experiencing problems with outgoing connections.

Also, it was stated that the network can see this node.

Side note: I recommend disabling the Server service on most NT Workstations.

Leaving the server service on complicates and lengthens the browse list. All you really need to see in Network Neighborhood are the servers and the few workstations (if any) running gateway or similar software. You needn't even browse local resources.

by eltoncole

...but NetBEUI would also have to be on the servers AND the browse masters.

Remember, you may get the browse list from a node other than the server you are connecting to. It may even be a workstation, not a server...

BTW, I set workstations (and Win 9x if in my environment) to not participate in browser elections. I also use the the "browstat" tool from the resource kit to make sure my browser preferrences are working correctly.

Actually, I set some servers like this too: Exchange, database, etc. I don't want my single purpose servers distracted with this activity.

I typically set up P/BDCs and file/print servers to be browse masters.

Also, NB is really only reliable on networks with 255 nodes. Freaky stuff on bigger nets.

by eltoncole

Forget about browsing for just a bit.

Issue some "net view" commands from a command prompt on that node.

Net View to:

* specicif servers
* specific domains

Try "net use" to known available shares on a known good server.

If you can connect via the "net" commands, you are 90% there. Then, look at your browsing setup. The browser service is running, yes?

There is good help for the Net command available from within the command prompt.

Side item. I highly recommend the book "Mastering NT V4" by Mark Minasi. Both the server and workstation versions are excellent.

I have carried Minasi's books with me on so many projects that they are falling apart. He tells the real world solutions and descriptions, not just the official MS view...

Craig Stinson also writes great NT/networking books.

by acs

I read throught he thread and agree with the submitter. When you installed, you probably were connected to the network and NetBIOS name forced a name block

by angler57

I think one of the posts almost hit on it..be sure that the ws has a computer acct on the PDC. The fact that the others can see the ws but the ws cant see the others leads me to beleive that there may not be an account for the ws.

by eltoncole

The node will have a NetBIOS name (machine name) exclusive of the protocol in use: IP, DLC, NWLink, AppleTalk, whatever.

MS LAN Mgr (which is, in great measure intrinsic in NT) assigns a NetBIOS name in a cursory manner.

There are MS NetBEUI hooks in all the available protocols. This is embedded so apps written with NB in mind can work with other protocols.

I did mention the possibility of duplicate NB name or IP address in an earlier post. The node would have generated an onscreen message and Event Viewer entry if either of these had occurred.

And, as I mentioned, not just the desktop node and target server wouild need NB, but the server(s) supplying the browse list would need a compatible protocol to inform the node of the resources available on the network.

by eltoncole

Is this node a new installation/rebuild/image?

Has it ever connected successfully to network servers?

Issue a "net use" command from the console and please report the results.

Make a copy of the logon script. Edit it to insert "pause" aftereach action ("net use M: \\server1\share2"). With the console (command prompt) open, manually run the logon script and check the results.

What is the proxy setup? If MS Proxy Server, are the node and proxy on the same domain?

Final, use a DOS network boot/connection disk (a known good disk). Boot from it and see if you can connect. This will check the hardware, NIC, cabling, etc. without going through NT OS.

On a positive note, my experience has been that the wider or more basic a problem is, the simpler it is. Not ironclad, but usually true...

by eltoncole

There are two method for this.

1. Change the node name (log on as domain admin at the node). Then change it back.

2. (works better, I believe) Change the node membership from the domain to a workgroup (log on as local admin on the node). Make up a new, unique workgroup (testnode).

Check the PDC. Delete the old node name, if existant.

Reboot the node. Join the domain.

If this doesn't work, check out the event logs on both the node and PDC.

by jhender31

I agree with pdc. sounds as if this workstation is not authenticated. It is likely you can ping anything in the world(depending on config)so connectivity is there. If this station has never been on the network(new install) did you join the domainusing the domains admin and password? I once had this happen on a new install and could not get the machine on the network without rerunning setup and joining the domain from there. We need more info; trusts..new install?...

by bozh32

make sure you have properly configured or added Microsoft Network components and added to your LAN or network, to PDC, with the right protocols. if you have Novell consider adding IPX protocol.

by anthonybernardino

1. problem is computer browser. Is it running on your domain controller? if so, you'll need to disable it on the workstation.
2. what's the subnet mask of your workstation? does it match up with the servers?

3. can you ping the server from your workstation and vice versa?

4. what class IP addressing scheme are you using? Class A? Class B? Class C? Did you calculate it correctly with the corresponding subnet on your server?

5. is your server configured to be a hidden node on the network? If so, do you have DNS or WINS running? If you have DNS or WINS running, go to START, RUN, in the command line type \\myworkstation. myworkstation is the hostname of your workstation.

That's it for now, if you should need further assistance, e-mail me: AnthonyBernardino@Engineer.com. I'll try to respond as soon as I can.

This discussion is closed to new replies.