PDA

View Full Version : Win2k Network Woes... help :)


etones
Thu 2nd Aug '01, 7:51am
Hi all, right im having problems allows some winme machines to connect to my network., heres my setup..

1) Windows 2000 Server
- DCHP Server
- Wins Server
- DNS Server

2) 3x Win2000 Clients...

Now, the Win2000 clients can all login to the network and see all the other computers and shares.

I have made each client dualbootable to WinME for gaming platforms...

However no WinME Systems can see the network... Each dualbootable system has the same NetBIOS name..eg under Win2k and WinME a system will be called STORM for example.

I have no idea what todo to.... The WinME clients act as if there isnt a NIC in the PCs, when Browse Network is opened, they error.

I have not setup a domain on the server, its tooo much for what i require, + the last time i tried to setup a domain system.. my network died :)

There is only one network Username and password, therefore when a PC logs in with the Username and Password, they have rights already available on all PCs....

Ahh, its driving me nuts, please help :)

If I need to supply more info please ask.

Thanks to all!! Cheers

JamesUS
Thu 2nd Aug '01, 8:11am
I think you need to give the computers different NetBIOS names under WinME and Win2k.
Might be wrong though :D

etones
Thu 2nd Aug '01, 8:24am
mmmm, i'll try an report back :)

cheers

etones
Thu 2nd Aug '01, 8:41am
ok...

I have a workgroup called Mistry that all the Machines are under...

The WinME client has now created its own Workgroup called Mistry and appeared in it.. however no Win2k Machines see it in there Mistry workgroup and the WinME machines doesnt see any toher machine... grr, i h8 networking :)

Martz
Thu 2nd Aug '01, 11:20am
WinME is horrible when you plug it onto a network - browsing Network Neighbourhood shows that it isn't connected to the network, but really it is.

One thing that worked for me: reboot the machine into ME, and open Network N'hood. If nothing shows, logoff, and then logon again. This process seems to force the NIC to scan the network again, and properly connect itself. I know its not a fix, but it might help.

etones
Thu 2nd Aug '01, 12:03pm
well, managed to fix it :)

WinME Clients wont get an Ip from the DHCP server, i had to set them all a static IP.. and they worked :)

Susan
Thu 2nd Aug '01, 12:16pm
Just FYI since etones already figured out that specific problem, www.practicallynetworked.com is a great resource if you're willing to dig down deep into the troubleshooting pages to get at your problem. It's fixed our network more times than I can count. (And probably will again tonight since every time we change out the cable modem, the network breaks.)

etones
Thu 2nd Aug '01, 12:19pm
cheers Susan, i'll keep that bookamrked!! :)