Can get on to internet, but not onto network

zecidnac · 04-05-2006, 11:11 AM

Greetings. I hope I've picked the right forum.

I've connected a new user to my network. Every machine on this network is running Windows XP. Our server is Windows 2003 Server (Appliance Server).

The trouble is this: We can get this brand new Windows XP machine onto the internet, but we cannot log him in to the network to access our resources.

On the server, I've created a new user under Users & Groups. I've added him to the very same users group that everyone else is in. I've also checked his permissions to make sure he's allowed to access these resources.

Now, when I go to another machine (like my machine or anyone else's but his) I can log on using his username and password. When I go back to his machine, I cannot log in. I know he has network connectivity, but I cannot for the life of me figure out why we can't get him to access our network resources or his own folder.

Spektyr · 04-05-2006, 11:22 AM

Have you double-checked that machine's networking properties to make sure they match everyone else's? Like making sure he's got NetBIOS protocols installed? (I just made that mistake earlier today.)

zecidnac · 04-05-2006, 11:27 AM

Quote:

Originally Posted by Spektyr

Have you double-checked that machine's networking properties to make sure they match everyone else's? Like making sure he's got NetBIOS protocols installed? (I just made that mistake earlier today.)

Thank you for your reply.

Yes. He has NWLinkNetBIOS installed. I clicked Install just to check, clicked protocols, and the only protocol in the list is TCP/IP Version 6

ebackhus · 04-05-2006, 11:58 AM

You may want to also make sure that TCP/IP v4 is also installed.

zecidnac · 04-05-2006, 12:04 PM

Quote:

Originally Posted by ebackhus

You may want to also make sure that TCP/IP v4 is also installed.

Thank you for your reply.

It is. What I was trying to say above is that the only protocol that ISN'T installed is TCP/IP Version 6. He's got:

Internet Protocol (TCP/IP)
Client for Microsoft Networks
File and Printer Sharing...
QoS Packet Scheduler
NWLink NetBIOS
NWLink IPX/SPX/NetBIOS Compatible Transport Protocol
Network Monitor Driver

Oh, and I forgot to mention that we disabled the firewall that came with the computer.

**leroys1000** · 04-05-2006, 06:15 PM

Right click my computer,click properties,click the computer name tab,
click the change button and make sure the work group name is
the same as the other computers.

Spektyr · 04-05-2006, 09:38 PM

Just thought of something else: the computer's network name doesn't have a space or some other non-allowed character in it, does it? If there's something like that (pretty much anything aside from letters, numbers, or a hyphen) it can make it so that other computers can't find it on the network... that might cause problems.

zecidnac · 04-06-2006, 06:55 AM

Quote:

Originally Posted by Spektyr

Just thought of something else: the computer's network name doesn't have a space or some other non-allowed character in it, does it? If there's something like that (pretty much anything aside from letters, numbers, or a hyphen) it can make it so that other computers can't find it on the network... that might cause problems.

The computer's name is Kenny. There are no characters, spaces, or anything in it that might cause a conflict. And we can successfully ping him by name.

Our workgroup is SALES, also with no spaces or characters. His computer can ping the server by IP and by name. The ONLY problem I'm having is not being able to physically log him in to our network with a username and password on THAT machine.

**Squashman** · 04-06-2006, 09:25 PM

Is this a Domain environment or Workgroup only?
If it is a Domain then you need to create a computer account on the domain controller and join the computer to the domain. Otherwise he needs a local username and password on the machine if it is just a workgroup environment.

zecidnac · 04-07-2006, 06:36 AM

The boss got impatient and reformatted the hard drive. Once he reinstalled the OS, assigned a static IP, and joined it to the workgroup, it went right on the network. It must have been something that Dell installed (McAfee?) that was preventing it from accessing network resources.

04-05-2006, 11:11 AM	#1 (permalink)
zecidnac Registered User Join Date: May 2005 Posts: 29 OS: windows xp	Can get on to internet, but not onto network Greetings. I hope I've picked the right forum. I've connected a new user to my network. Every machine on this network is running Windows XP. Our server is Windows 2003 Server (Appliance Server). The trouble is this: We can get this brand new Windows XP machine onto the internet, but we cannot log him in to the network to access our resources. On the server, I've created a new user under Users & Groups. I've added him to the very same users group that everyone else is in. I've also checked his permissions to make sure he's allowed to access these resources. Now, when I go to another machine (like my machine or anyone else's but his) I can log on using his username and password. When I go back to his machine, I cannot log in. I know he has network connectivity, but I cannot for the life of me figure out why we can't get him to access our network resources or his own folder.

04-05-2006, 11:58 AM	#4 (permalink)
ebackhus Manager, Design Join Date: Apr 2005 Location: SATX Posts: 15,069 OS: WinXP Pro SP3/Windows 7 RTM My System	You may want to also make sure that TCP/IP v4 is also installed. __________________ ----------------------------- There are no dumb questions, unless a customer is asking them. Help in the fight against cancer and other serious illnesses.

04-05-2006, 06:15 PM	#6 (permalink)
leroys1000 Tech Join Date: Aug 2005 Posts: 770 OS: Windows XP	Right click my computer,click properties,click the computer name tab, click the change button and make sure the work group name is the same as the other computers. __________________ There is a madness to my method.

04-07-2006, 06:36 AM	#10 (permalink)
zecidnac Registered User Join Date: May 2005 Posts: 29 OS: windows xp	The problem has been resolved. Thank you to all who responded. The boss got impatient and reformatted the hard drive. Once he reinstalled the OS, assigned a static IP, and joined it to the workgroup, it went right on the network. It must have been something that Dell installed (McAfee?) that was preventing it from accessing network resources. Last edited by zecidnac; 04-07-2006 at 06:38 AM.

04-05-2006, 11:22 AM	#2 (permalink)
Spektyr Registered User Join Date: Mar 2006 Posts: 102 OS: XP, Vista Home & Ultimate / Ubuntu "Hardy Heron"	Have you double-checked that machine's networking properties to make sure they match everyone else's? Like making sure he's got NetBIOS protocols installed? (I just made that mistake earlier today.)

04-05-2006, 09:38 PM	#7 (permalink)
Spektyr Registered User Join Date: Mar 2006 Posts: 102 OS: XP, Vista Home & Ultimate / Ubuntu "Hardy Heron"	Just thought of something else: the computer's network name doesn't have a space or some other non-allowed character in it, does it? If there's something like that (pretty much anything aside from letters, numbers, or a hyphen) it can make it so that other computers can't find it on the network... that might cause problems.

04-06-2006, 09:25 PM	#9 (permalink)
Squashman Microsoft MVP Join Date: Apr 2005 Location: 1265 Lombardi Ave. Posts: 1,180 OS: All of the above	Is this a Domain environment or Workgroup only? If it is a Domain then you need to create a computer account on the domain controller and join the computer to the domain. Otherwise he needs a local username and password on the machine if it is just a workgroup environment.