Win2k Pro, cannot see the workgroup computers 1

[ame540]

Hello.

Super basic problem, not sure what the fix is.

We have a windows 2000 professional computer in our warehouse for DHL shipments. I need it to see the workgroup so that it can print to a shared printer. However, It cannot see any of the other computers in the workgroup, except itself. I cannot connect to it through network neighborhood, but it is pingable. Conversly it can ping me, but doesnt see any computers in the neighborhood.

Things ive tried.
Uninstalled / reinstalled, NetBios, Netbeui, File and Printer sharing.
They are on the same subnet, and i can ping / have internet access through our gateway.

any more suggestions? Thanks!

 

[bcastner]

. Make sure it has a username with password. You can use autologon, but be certain there is a password.
. Make sure that File and Printer Sharing, and that 'Enable NETBIOS over TCP/IP' are enabled on the connection. Netbios is enabled through TCP/IP Properties, Advanced, WINs tab.
. Share something, anything: drive, folder, printer but something on all computers.
. If that is not sufficient, add the username and password for the DHL workstation as a new local user with the same username and password on the computer that hosts the printer.

 

[bcastner]

I note that if Netbui cannot see the other workstations, you could well have a cabling issue. If you Start, Run, CMD

Type:

net view

You should see all the workstations on the network if there is no logical or cabling issue.

 

[ame540]

bcastner...

alot of good information.
The DHL computer does have a login "Administrator" and a password. It has the C drive shared, with access for Everyone. So far no luck. I will be checking the Netbios portion and see if the net view command finds anything...

 

[ame540]

ok so the original problem was that i was getting the message when trying to view the network neighborhood:

"workgroup is not accessable.
the list of servers for this workgroup is not currently available"

So then i installed netbios, etc. And it doesnt give me this message anymore, it just finds itself.
now, TCP/IP > Advanced > Wins Does have enable netbios over TCP/IP selected. However i dont know why this would matter as we dont use a WINS server.

Still i get this message when using the net view command, (similar to what happens when i use the network neighborhood to browse)

\\DHLSHIPPING (the computer name)
the command completed successfully.

but only 1 computer....
im lost.

 

[bcastner]

This message usually indicates that the Workgroup name of the computer is different than the other Workgroup stations. Check the upper and lower case, the spelling, make sure it is less than 12 characters in legth.

The second cause is if you have more than one protocol established. Eliminate Netbui from all workstations and reboot them all.

 

[ame540]

One thing i am sure of is that the workgroup name is the same, i even added a different one the changed it back. (rebooting each time of course). I will uninstall Netbeui from this computer.

As for all the other ones, that might not be possible right now.

 

[bcastner]

It is clearly a Browser issue. See member Bob Linn's notes under "Browsing":

http://www.chicagotech.net/

Cleaning the protocol stack seems wise. A repair of the Winsock service stack is also advised, see faq779-4625

A final note: lets say the workstation hosting the printer is called "Printer." Start, Printers and Faxes, Add a new printer, network printer, browse, and give the address \\Printer

Can you find and make a printer connection?

 

[ame540]

Negative. There are not networked printers found. This makes sense as that workstation cannot find any of the other PCs that the printers are attached to. I will uninstall / reinstall the TCP / IP stack. See what happens.

 

[ame540]

We figured it out.

Thank you Bcastner heres your star.

The TCP/IP stack must have been corrupt, as i uninstalled it and reinstalled. It was finally able to see the rest of the network without Netbeui or NetBIOS installed. Just client for microsoft networks and File / Printersharing for MS networks. All is good! im happy and so is my shipping department.

 

[bcastner]

Excellent.

This should not be that hard.

Best wishes,
Bill Castner