Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
cannot browse network computers
- Thread starter poludeh
- Start date
- Thread starter
- #3
- Thread starter
- #5
Yes the Server service is running. Both clients and servers cannot browse clients an servers on the network 
, except some win98 users 2/3 of 30. My servers are win2k, and most of users are on winXP and some win98
I dont have WINS server.
Do you think that the reason can be in domain groups which i create a week or two before this problem starts?
, except some win98 users 2/3 of 30. My servers are win2k, and most of users are on winXP and some win98 I dont have WINS server.
Do you think that the reason can be in domain groups which i create a week or two before this problem starts?
No, I don't think its the groups. I think it is a problem with NETBios. If you look at your network properties, do you have both "Client for Microsoft Networks" and "File and Printer Sharing for Microsoft Networks"? Do you have anything blocking ports 135-139? Did you happen to install McAfee Virusscan 7 recently?
- Thread starter
- #7
yes i have "Client for Microsoft Networks" and "File and printer sharing for MS". Never install McAfee. I didn't install newer software.
Ports opened are:
TCP ports - 7 open ports
135 [ epmap => DCE endpoint resolution ]
139 [ Netbios-ssn => NETBIOS Session Service ]
445 [ Microsoft-Ds ]
3389 [ Terminal Services ]
5800 [ VNC => Remote Control Software ]
5900 [ Microsoft VNC ] RFB 003.003
10000 [ Webmin => web-based interface for system
UDP ports - 4 open ports
137 [ Netbios-NS => Netbios Name Service ]
138 [ Netbios-DGM => Netbios Datagram Service ]
445 [ Microsoft CIFS => Common Internet File]
1434 [ ms-sql-m => Microsoft SQL Monitor ]
Ports opened are:
TCP ports - 7 open ports
135 [ epmap => DCE endpoint resolution ]
139 [ Netbios-ssn => NETBIOS Session Service ]
445 [ Microsoft-Ds ]
3389 [ Terminal Services ]
5800 [ VNC => Remote Control Software ]
5900 [ Microsoft VNC ] RFB 003.003
10000 [ Webmin => web-based interface for system
UDP ports - 4 open ports
137 [ Netbios-NS => Netbios Name Service ]
138 [ Netbios-DGM => Netbios Datagram Service ]
445 [ Microsoft CIFS => Common Internet File]
1434 [ ms-sql-m => Microsoft SQL Monitor ]
- Thread starter
- #9
- Thread starter
- #11
aroggeband
Programmer
- Make sure that all machines are configured for domain and not workgroup access.
- Also make sure that all win98 machines are using Windows Client set up for domain access and using Windows file and print to share files.
- Make sure that "browse master" is disabled in file sharing on all win95/98 machines.
- Also make sure that any WinNT/2000/XP/2003 machines on the network are properly joined to the domain. A machine misconfigured for workgroup access (by some helpful user) may grab the browse master role.
I have seen something similar three times.
The first was in a mixed Novell/Windows workgroup environment. When individual Win98 machines were misconfigured to use Novell file sharing and the windows login client, or Windows file share/Novell client, all the other machines would hang and timeout when browsing the network, presumably when attempting to browse the offending machine. This resulted in empty browse lists.
The second time was in a "pure" windows 2K domain. In "File and printer sharing" properties "Browse master" on many windows 98 machines was set to automatic. This caused browse failures when for some reason they grabbed the role of "browse master". Some of them were set to workgroup access instead of domain membership, with our domain set as the workgroup name. The result was that only Win98 machines were visible when browsing.
The third time, on the same windows 2k domain as the second, our consultant set his Windows 2003 server up by VPN. It was configured as a workgroup with the workgroup matching our domain name. When browsing, sometimes all machines and sometimes only the 2003 server were visible.
(bard+math)-->2b|^2b=?
- Also make sure that all win98 machines are using Windows Client set up for domain access and using Windows file and print to share files.
- Make sure that "browse master" is disabled in file sharing on all win95/98 machines.
- Also make sure that any WinNT/2000/XP/2003 machines on the network are properly joined to the domain. A machine misconfigured for workgroup access (by some helpful user) may grab the browse master role.
I have seen something similar three times.
The first was in a mixed Novell/Windows workgroup environment. When individual Win98 machines were misconfigured to use Novell file sharing and the windows login client, or Windows file share/Novell client, all the other machines would hang and timeout when browsing the network, presumably when attempting to browse the offending machine. This resulted in empty browse lists.
The second time was in a "pure" windows 2K domain. In "File and printer sharing" properties "Browse master" on many windows 98 machines was set to automatic. This caused browse failures when for some reason they grabbed the role of "browse master". Some of them were set to workgroup access instead of domain membership, with our domain set as the workgroup name. The result was that only Win98 machines were visible when browsing.
The third time, on the same windows 2k domain as the second, our consultant set his Windows 2003 server up by VPN. It was configured as a workgroup with the workgroup matching our domain name. When browsing, sometimes all machines and sometimes only the 2003 server were visible.
(bard+math)-->2b|^2b=?
- Thread starter
- #13
I found one machine with XP that have problem with propertly joining the doman.
It the "Member of" is shown "domain name"-the right one, not a workgroup, but when i try to share a folder with user permisions-there is not domain users available from the server.
Is this the computer which is f...ing with me?
I don't know, i'll try to fix some win 98 machines for browsing masters.
It the "Member of" is shown "domain name"-the right one, not a workgroup, but when i try to share a folder with user permisions-there is not domain users available from the server.
Is this the computer which is f...ing with me?
I don't know, i'll try to fix some win 98 machines for browsing masters.
aroggeband
Programmer
Maybe it is the one.
Fortunately, XP doesn' sc**w up the user profiles when rejoining to the domain. W2000 is a bit more complicated.
One important clue to the problem is that it began while you were on holiday. Everything was working properly when you left and broke while you were gone. Give the 3rd degree to the person in charge while you were gone. Find out what problems or changes happened in that time. Perhaps some "home networking genius" attempted to (re)configure something without understanding windows domains. Maybe someone ran an attachment from their email :-o .
(bard+math)-->2b|^2b=?
Fortunately, XP doesn' sc**w up the user profiles when rejoining to the domain. W2000 is a bit more complicated.
One important clue to the problem is that it began while you were on holiday. Everything was working properly when you left and broke while you were gone. Give the 3rd degree to the person in charge while you were gone. Find out what problems or changes happened in that time. Perhaps some "home networking genius" attempted to (re)configure something without understanding windows domains. Maybe someone ran an attachment from their email :-o .
(bard+math)-->2b|^2b=?
bierhunter
IS-IT--Management
Just wanted to throw in this bit about the DHCP.
You want to know who is using what IP address. I can understand that completely. You can still use DHCP and have the same information.
Using DHCP on your server will allow you to manage your addresses from a central point and not have to run around to the workstations. You will have more control over them as well.
The DHCP server will tell you which PC has which IP address. If you need to assign specific addresses to specific computers, just reserve their MAC address on the server and assign it an IP address on the DHCP server. Then, that machine will always get the same address that you gave it.
The nice thing about that is that you now have a listing of all machine names, MAC addresses, and IP addresses at your fingertips and never have to leave your desk. If you need to make changes, you just it do from your own keyboard. You will still have all of the information and control you need.
I just think that it would make your life easier, and still give you the admin control you want.
BierHunter
CNE, MCSE, CCNP
You want to know who is using what IP address. I can understand that completely. You can still use DHCP and have the same information.
Using DHCP on your server will allow you to manage your addresses from a central point and not have to run around to the workstations. You will have more control over them as well.
The DHCP server will tell you which PC has which IP address. If you need to assign specific addresses to specific computers, just reserve their MAC address on the server and assign it an IP address on the DHCP server. Then, that machine will always get the same address that you gave it.
The nice thing about that is that you now have a listing of all machine names, MAC addresses, and IP addresses at your fingertips and never have to leave your desk. If you need to make changes, you just it do from your own keyboard. You will still have all of the information and control you need.
I just think that it would make your life easier, and still give you the admin control you want.
BierHunter
CNE, MCSE, CCNP
- Status