11 replies
by mr_fixit
by mr_fixit
by kza_iran
please send me your complete pic of network properties dialog tabs. do u have "client for microsoft network" as ur "primary network logon"? did u configure logon validation on "client for microsoft network" properties dialog?
sincerly yours,
k.zonouzi ahmad
by mr_fixit
Yes, here is the complete config:
Client for MS Networks, Log onto NT Domain (Specified)
3Com NIC
TCP/IP
File and Print Sharing
Identification: Machine Name specified, Domain Specified, User Name as the description.
Access Controlis set to User Level with the Domain specified.
{{The rating scheme here is limited. Helped or not.}}
by ezmoney
by mr_fixit
Yes, here is the complete config:
Client for MS Networks, Log onto NT Domain (Specified)
3Com NIC
TCP/IP
File and Print Sharing
Identification: Machine Name specified, Domain Specified, User Name as the description.
Access Control is set to User Level with the Domain specified.
{{The rating scheme here is limited. Helped or not.}}
Win9x clients need NetBIOS to identify the domain controllers on a network.
If you are running a WINS server, the DHCP server should have the appropriate records pointing the clients to the WINS server.
If there is no WINS server, all clients should be configured to broadcast mode. On a small network broadcast traffic may be tollerable, at some point it will become excessive and a WINS server should be placed into service.
Win9x clients must be configured for NetBIOS over TCP/IP.
It sounds like you have incorrect NetBIOS information being delivered to the clients, you should review server and client settings in detail, including reviewing any WINS database records that may be present.
by mr_fixit
by deltree
We had a similiar issue with our roaming laptop users. When they went to a different subnet they did not receive a new IP from DHCP, instead, keeping their old one from a different subnet. Using release all and renew all worked every time but at the annoyance of the end user.
It turned out to be the 'spanning tree' protocol on our Nortel switches. When active, there is an autodiscovery period when new devices attach. The device can send a (DHCP) broadcast through the switch, but the switch will not send any broadcasts back through that port until the autodiscovery phase is complete.
We disabled the protocol on all our switches which fixed the problem.
by mr_fixit
by mr_fixit
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending