Jump to content

Bitmapped

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

0 Neutral

About Bitmapped

Personal Information

  • Occupation
    Course Coordinator
  • Location
    Morgantown, WV

Employer (optional)

  • Company Represented
    West Virginia University
  1. Well, a clarification I guess. I have seen the log entries on the Intels but it is the Broadcoms that have been causing bigger usability problems. I've been through a variety of different driver versions and settings for auto-negotiation, although I haven't tried anything like "wait for link." I'm not seeing a setting like that on the Broadcom drivers. I've been loathe to disable allowing Windows to turn off the NIC because that also means my ability to Wake-on-LAN the computers goes away. A question: With this issue are you just seeing the log entries and/or Group Policy failures or are you getting real logon errors? For the Broadcoms, when users try to logon I will intermittently get "no logon server is available to service the logon request" if they try to use a domain account. As I mentioned above, if I login with a local account Windows acts like it is trying to get an IP/identify the network then it seems to give us and say we're unplugged.
  2. We basically have two groups of PCs, Dell Vostro 200s with Intel NICs and Vostro 230s with Broadcom Netlink 57xx NICs. The Intel NICs seem fine, it's the Broadcom ones that are having problems.
  3. I've been running into a case I think might be related to this issue. Win7 SP1 x64 machines joined to a domain, get their IPs through a Cisco helper. On system wake (seen it from sleep, not sure from full boot) have intermittent issues with "no log on servers" error. NIC shows it has a connection, but if I log in with a local account Windows tries to get an IP then gives up and actually tells me the network connection is unplugged. Reboot generally solves the problem. I went through the directions in the MSKB article and on my systems at least, the TCP-IP interface already had the force broadcast flag set to 1. I've tried different drivers and autonegotiation settings without luck. Trying now to disable the public-profile firewall in case that's the isuse. Any word on when Microsoft might make this hotfix available so I can test that? Trying to track down these issues in two computer labs is driving me crazy.
×
×
  • Create New...