Can't change workgroup name

[Hodgepodge]

A buddy came by yesterday and tried to connect to my network. When we went to the Computer Name tab under System Properties, and clicked Change, the section under Member of was grayed out. Also, the Network ID button was also grayed out.

We also couldn't get a valid LAN IP thru DHCP. We kept getting something in the 169.xxx.xxx.xxx range, with a subnet mask of 255.255.0.0. I run class B LAN IP's, with a subnet mask of 255.255.255.0. We finally hardcoded static IP's but we still couldn't get to the Net. Nor could he ever connect to my network.

This is a Dell Inspiron laptop running Windows XP SP1. And we were trying to connect with a wire as opposed to wireless.

What could've happened? He swears he hasn't touched anything.

TIA

Hodgepodge

Why doesn't this work?

 

[wolluf]

on the more info front - what does the network he's trying to connect to consist of? (domain/workgroup, how many machines, how is internet connected - router, ICS etc. Do you have a DHCP server)

How is he connecting to your network (eg, have you got the right patch cable)?

also - is his network card working properly?

 

[bcastner]

You are running a Class C network, not a B. Look at your network mask again.

He cannot change the settings you wanted because either he is a member of a Domain already, and the Domain Policy settings are unavailable unless he is an member of the Administrator Domain Controller Group, or, he is using XP Home edition.

You do not need to change any domain or workgroup settings in any case to enable him to join your Lan.

If he was joined to a Domain you would need to make certain that he logged in to the local console and not the Domain console. He should log in as the local administrator user.

 

[Hodgepodge]

Hi Wolluf, thanks for your reply. He's trying to connect to a Workgroup of 8 machines. I connect thru a router and because of laptop friends, I enable DHCP on the router. He brought with him a 10' straight-thru cable, but we also tried the one I was using to no avail. To be honest, I didn't check to make sure his nic card was working, but he states although he hasn't used the laptop in a few days, it was working at that point.

Hi Bcastner, thank you also for your reply. I run static IP's on the LAN side, and the IP's are 172.16.20.xxx
with a subnet mask of 255.255.255.0. What we couldn't change was his own Workgroup name, which was grayed out as well. This is a friend I've known for years, and he wouldn't know how to spell D.O.M.A.I.N.

Again, I apologize for not providing enough info to come up with a solution.

Thanks again!

Hodgepodge

Why doesn't this work?

 

[Hodgepodge]

I forgot to mention that the laptop is running WinXP Pro.

Why doesn't this work?

 

[smah]

Try Start, Run, services.msc

See if the Remote Access Connection Manager is running. If not try to start it. If it doesn't start, see this MSKB article

http://support.microsoft.com/default.aspx?scid=kb;en-us;329441

If it is running, nevermind.

 

[bcastner]

Start at the level of configuring the NIC. I do not think you get the Workgroup/Domain selection until Client for Microsoft Networking is applied to the adapter. As it is unclear that a DHCP server is still runnin on the router (if you are running all static IPs you might as well shut it off to prevent scoping issues), assign an exclusive static IP.

Checklist:
1. Bring up the properties for the card. Use the configure button to force a 10-half connection if to a hub, 100-full if possible on a switch. Do not let it do Auto.

2. Add if not there presently:
Client for Microsoft Network
File and Printer Sharing
TCP/IP

3. Configure the static ip, be sure to set the Gateway to the router's IP. Set the DNS entry to the Gateway of the router as well. Hit the Advanced button. Under the WINS tab disable LMHOSTS and enable Netbios over TCP/IP.

4. Now right-click My Computer, Properties and try to set the computer name. It should allow it. If it does not reinstall the Network Components. He may have missed one. Control Panel, Add/Remove Programs, Windows Components, uncheck Network Components. Apply. Go back in and check Network Components (look at subcomponents as well) Apply. This forces a reload of the Networking Components.

5. Make on quick pass through adapter properties to make sure all is okay.

Reboot.

Start a CMD session.
ping 127.0.0.1 (Test his hardware layer)
ping 172.16.20.? (Test connection to router IP)
ipconfig /all (look at the settings again)

If he fails all these tests again, I say bad hardware and/or bad cable.


Remember to add his user name to shared resource computers.