PDA

View Full Version : WTF? 98/NT clients refuse to talk to 2003 servers

Rooster
03-13-2005, 02:57 AM
WTF?

I thought i knew all the possibles answers to this one..

Directory Services Client
Disable SMB Signing on the server
Enable SMB signing on the client
WINS
DHCP Auto-register DNS
LMHOSTS (w/ #PRE & #DOM)
HOSTS
Enable NETBIOS over TCP/IP (on client & server)

I looked at the default adm policies but didn't see anything that might help me.

They all talk to the 2000 Server (DC) (which has had it's Schema & Domain upgraded to 2003) - but NOT either of the 2003 servers (one is a DC, the other is just a file server).

Before a reboot, a few NT boxes could see them, after reboot - nada. It can see it in the browse master list (Network Neighborhood), but can't acces them.

All the Win2k & XP clients work great.

Me and my boss spent about 7 hours banging our heads on this one.

I know it can be done. But SOMETHING is not misconfigured/configured too strictly. I just have no clue what it is.

I'm thinking it's server side though.
MickeyFinn
03-13-2005, 03:29 AM
Have you tried switching out hardware at all? I'm a noob, but that seems like where I'd go next
Rooster
03-13-2005, 11:24 AM
In the server? It's not server hardware when all the 2k & XP machines talk fine.

In the clients? Most of them are in machine control terminals (they control large machines that tool & form tire molds) - and they talk to fine to Win2K server.

It's got to be a 2003 network traffic security setting.
Rooster
03-13-2005, 11:36 AM
Firewall is disabled on both 2003 servers.

Only one NT had IPX/SPX. Had no effect when I disabled it.

All 9x & NT have NetBEUI on them. The Server 2003 doesn't - installing it requires a workaround I'm not sure I want to go through with due to some special packet filtering we're running on the file server (no packet filtering on the 2003 DC) to prevent two identical machines (redundant file servers) from being on the network at the same time. This may be our only real option however. However, with NTSP6 & the DS client & 98 w/DS client - they SHOULD all be talking fine over TCP/IP.

I configured the DHCP myself and verified that DHCP was indeed supplying the correct DNS suffix.

I looked at the SET & IPCONFIG replies as well.
Their logon server was the 2000 DC (still has all FSMO roles).

I've even rearranged the binding order to no avail.
spyder913
03-13-2005, 04:16 PM
are you running IPSec at all?
Rooster
03-13-2005, 08:01 PM
Not required... (requested, but not required)

I just talked to my boss - turns out it was combination of things:

Disabled SMB signing (as I thought)
And WINS Scope was defined in DHCP. Took that out, and it works.
spyder913
03-13-2005, 10:52 PM
(I hate wins)

AD dns works so much better
Rooster
03-14-2005, 12:01 AM
Yup. WINS sucks, but NT & 98 love it. :(

Ugh for old technology.

New technology has made me lazy :)
Boom
03-14-2005, 02:47 PM
That stuff is crazy. Everything should be plug and play. When you plug the computers into each other they should automatically start talking to each other and configure themselves up correctly. I can't believe that Bill Gates got to be the richest man in the world selling this crappy, overly complicated operating system.
spyder913
03-14-2005, 02:56 PM
Yeah that would be secure ;)
Elvtin
03-14-2005, 10:43 PM
I'd just like to say that I just installed Win2k3 SErver and am getting to play with it. :)
Rooster
03-14-2005, 10:46 PM
It's great. Just hate it when mixing with really old stuff.

With 2K & XP - it's great.