Re: Forcing Duplex settings

I'm not sure if we have tested it in an testlab enviroment.
The system is already running in production, and there is alot of resources
we need to get to do an testlab.

I'll take your tip and ask the WMI list, or atleast read the FAQ :)

Thx for the help.

Kenneth
"Gerry Hickman" wrote:

> Hi Kenneth,
>
> The problems I had, were that I thought I was being clever matching the
> NIC to the switch (and it even recommends this in a manual I have), but
> when I tested it, everything to do with the network was messed up. I
> then put it back to "Auto" and everything started working again. I've
> never worked out the reason. I basically did it on each machine manually
> back then.
>
> In terms of "how" to force the settings, I don't know. It may be a case
> of hacking very specific registry keys for the NIC driver in question,
> or there may be a way to use NDIS API calls, or the NIC maker may have a
> developers guide or WMI provider.
>
> You may want to post about this on the WMI newsgroups if you don't get
> an answer here - although I don't think it can be done with WMI, the
> guys in that group know about this kind of thing.
>
> About your specific problem, did you try taking five clean built
> machines off the network and creating a test network with just those
> five? This is the first thing I'd do. You haven't exactly defined the
> problem very well.
>
> Kenneth Fossen wrote:
>
> > Hi,
> > What kind of problems have you been experiencing when you set the NIC's to
> > 100Full insted of Auto?
> >
> > The problem I have has a long story, but the only thing that did make the
> > situation better was when we set the NIC to 100Full insted of Auto, the same
> > on the switchport.
> >
> > And then we have tried almost everything, well it feels like you have tride
> > everything. But we switched nic's, cabels, new hardware for the computer and
> > new switches.
> >
> > Kenneth
> > "Gerry Hickman" wrote:
> >
> >
> >>Hi,
> >>
> >>Are you sure you know what you're doing, I've seen serious problems when
> >>it's forced, even though it was matched to the switch.
> >>
>
>
> --
> Gerry Hickman (London UK)
>
.

Relevant Pages

  • Re: Forcing Duplex settings
    ... The problems I had, were that I thought I was being clever matching the NIC to the switch, but when I tested it, everything to do with the network was messed up. ... It may be a case of hacking very specific registry keys for the NIC driver in question, or there may be a way to use NDIS API calls, or the NIC maker may have a developers guide or WMI provider. ... What kind of problems have you been experiencing when you set the NIC's to 100Full insted of Auto? ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: See if network is down?
    ... > connect through hub (switch) and you'll unplug from the hub(switch ... Unless I am mistaken this site uses WMI polling which is wasteful. ...
    (microsoft.public.win32.programmer.networks)
  • Re: Switch between 10Mb and 100Mb
    ... I was thinking it would have to be WMI. ... Advanced tab of a network port, ... I've got a need to be able to switch, or set the speed for my NIC between ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: See if network is down?
    ... If you check that polling in compare with WMI notifications you'll see twice ... >> connect through hub (switch) and you'll unplug from the hub(switch ...
    (microsoft.public.win32.programmer.networks)