I heard a Cisco Instructor once say: Auto = "Auto not do it"
""Kevin Wigle"" <[EMAIL PROTECTED]> wrote in message
009301c0032c$66728740$[EMAIL PROTECTED]">news:009301c0032c$66728740$[EMAIL PROTECTED]...
> I had a similar incident recently with a W2K server.
>
> If it had to be rebooted, it came back up ok but the weirdest thing was
that
> Win95/98 clients couldn't log in but W2K Pro clients could.
>
> To top it off, Win95/98 clients could ping the server so "IP" was good.
>
> To fix it we would just reboot the server again until it "took". Of
course
> this wasn't very satisfactory.
>
> The end story was that the nic on the server was set to auto. Once we set
> it to manual on 10BaseT everything worked fine.
>
> I have always suspected anything that has "auto" associated with it.
>
> Kevin Wigle
>
> ----- Original Message -----
> From: "David Jones" <[EMAIL PROTECTED]>
> To: "'John Neiberger'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Thursday, 10 August, 2000 17:20
> Subject: RE: Ethernet Troubleshooting Woes
>
>
> > The first thing I would suggest is don't assume too much. Usually, when
> > you're getting alignment errors and CRC's on a Cisco switch, it means
that
> > there is a mismatch between the switch port and the NIC's speed/duplex
> > settings. Configure the switch port that the server is on and hardcode
it
> > for speed/duplex settings. Here's an example:
> > conf t
> > int fa0/1
> > speed 100
> > dup full
> >
> > Try one thing at a time. You would be amazed at what something so
simple
> > can affect you.
> >
> > HTH
> >
> > Dave
> >
> > -----Original Message-----
> > From: John Neiberger [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, August 10, 2000 3:56 PM
> > To: [EMAIL PROTECTED]
> > Subject: Ethernet Troubleshooting Woes
> >
> >
> > Okay, I'm going completely out of my mind. I am at the end of my rope
> with
> > this problem and I have no idea where to go from here. Basically, I'm
> > begging for suggestions!
> >
> > Several PCs at one of our branches are having difficulty running a
certain
> > application, which uses IPX on 802.3 frames. We are also running IP on
> this
> > LAN with arpa frames. There is a file server and printer on this LAN,
and
> > all IPX traffic is between the hosts and that file server.
> >
> > We are have ZERO problems with IP traffic on this LAN. I've been
pinging
> > the tar out the hosts and they act perfectly normal, except for the file
> > server which had, at worst, a 98% success rate over time.
> >
> > On our ethernet switch, we are seeing alignment errors and CRC errors
> coming
> > from the file server. The cable has been replaced and we verified that
it
> > is cat 5, but the problems still exist. This is a new file server with
a
> > new NIC.
> >
> > Okay, the problem is that this particular application takes forever to
run
> > from a desktop out in the building. yet, if you bring that very PC back
> to
> > the room where the switch is, the application runs very quickly. This
led
> > us to believe that the cabling was bad. However, if the cabling were
bad,
> > why are we having no problems with IP traffic? None at all! That just
> > doesn't make any sense to me.
> >
> > Granted, the cabling out to the desks is Cat 3 and this branch has had
> some
> > previous EMI problems in the room, but I just don't see how EMI could
> > selectively cause one application to fail without there being some
> > indication of problems with other applications.
> >
> > I've considered replacing the switch, but the problem only happens when
a
> PC
> > out in the main room uses the application, no matter what port it is
> > connected to. Bring a PC back to the switch room and connect it to any
> port
> > and the program runs as advertised. So, I'm not going to waste my time
> with
> > that. I've also considered replacing the NIC in the server since we're
> > seeing errors coming from it, but that would not explain the problems
> we're
> > having, anyway, so that is probably pointless.
> >
> > any ideas? Our next step is to hire a very expensive data center design
> > company to go up there and check things out. We've had electricians
check
> > the room and they said they could find no obvious sources of EMI, even
> > though we know that it is prevalent there.
> >
> > Help...please help....I'm dying here, and I'm quickly losing faith in my
> > troubleshooting skills!
> >
> > TIA,
> > John
> >
> >
> >
> >
> >
> > _______________________________________________________
> > Say Bye to Slow Internet!
> > http://www.home.com/xinbox/signup.html
> >
> > ___________________________________
> > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> > FAQ, list archives, and subscription info: http://www.groupstudy.com
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
> > ___________________________________
> > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> > FAQ, list archives, and subscription info: http://www.groupstudy.com
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
>
> ___________________________________
> UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info: http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> ---
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
