Sounds like a nice feature
Nathan has a problem. As you may know, he's just bought a HP Procurve 2650 switch. The server is connected directly into the switch gigabit port, and a couple of switches down the line, in a room of mixed 98 XP machines, the 98 machines won't connect to the network.
Sounds like a nice feature
lol sounds like spanning tree protocol to me possibly
Yep. STP, VLAN or possibly traffic shaping configuration is screwed up.
what a day!
Its a HP ProCurve 2626 (not 2650) but whats 24 ports between friends eh? lol]
Also, its all the win 98 pc's in the entire school that suddenly cant log on anymore - the DC [was] attached to this new switch so it doesnt appear to be limited to any particular room or anything.
@andy: not a nice feature - not when u have no choice and management do feel the need to buy xp licenses for them lol
I found something in the web interface of the switch regarding it [was set to off so I turned it on but no change]
I've tried all sorts
- VLAN - dont use them
- traffic shaping config [whats that?? lol]
The HP ProCurve support line was puzzled - they said that if the switch is on the factory settings, then its pretty much like a unmanaged switch. It shouldnt stop 98 logging on to the network in any case.
He said he'd get back to me in the morning [which was nice] but didnt seem to think it would be the switch.
I think he's right as I've taken off all the connections on that switch now and the same thing is happening still
The other changes that have taken place are some firewall [router/vpn unit] rule changes - but I've reversed the changes now to my knowledge.
Also, yesterday afternoon, I attached a exchange 2003 server to the domain and I'm wondering whether this could be the cause [its looking like a definate] but I'm clueless as to why that would stop the 98 machines from logging onto the DC :S
I know that during the exchange install, it changes the schema of the AD but could this have done it and does anyone know anything on this and what to look for?
I soooo hate my job at the moment lol
Are all the 98 machines of the same make or similar hardware? Sometimes dodgy NIC chipsets can do this.
In my last job we had 3COM switches which would decide to stop talking to the Realtech chipsets on the 60 Gigabyte boards that we had. This happened intermitantly and randomly and I had to power cycle the switches.
Try sticking a different NIC into one or updating the drivers.
Hey, if it is the NICs, explain that it's going to cost ¬£20 per machine to remedy the problem and you may get the extra money for your XP Pro upgrade licenses.
good thought but alas no...
all different hardware really - about 30 of one type of machine, another 8 or so of another type, about 3 of another type and then various others.
Same with the switches really - theres alsorts all over the place. Like in my cat5 cabling network post, I'll try and russle up a map shortly
When you say they cant log on, have you checked if they have physical connections (ie are the status lights flashing on the switch and the card), and if DHCP is picking up? Try assigning a static ip address to one of the clients if you have a physical connection. If that does not work, try changing the port negotiation to a fixed setting like 100mbit full duplex then do the same on the client. If all of that fails then im stumped right now, but ill have a think about it...
Before you added the Win2003 server, what were the DC(s) running?
The Windows 95/98 networking client won't authenticate against a 2003 server...
It will if you install the MS gubbin that allows this - can't remember what it is right now but I did this at a primary school.Originally Posted by Westbrooke
Same here Ric- we still have those relics (98 machines) on our network and though they can be painful they do indeed authenticate against a 2003 server...
@kingswood: Can you remember the name of that gubbin?
That's the gubbin!
Some info here:
its on the w2k server CD.
There are currently 1 users browsing this thread. (0 members and 1 guests)