I am trying to solve a networking problem for someone. 5 computers on the network behind a router. all the computers can ping each other by IP address but only 3 of them can talk to each other via machine name (IE Ping sys1). Windows Firewall is turned off. One system is running mcafee firewall and the other is running norton. Disableing the firewalls has not seemed to help althoug the firewalls are configured to trust the local network.

Problem first occured after the machines were put onto another workgroup and network, then returned to the normal one.

All machines are members of the same workgroup.
One machine is running XP Pro and the other is running XP Media Center. I believe all service packs are current.
I have tried changing the workgroup to something new and then back
releasing and renewing ip address
ipconfig /flushdns
I was able to get the two machines that won't talk to the server to talk to each other by changing the workgroup.

Any suggestions? This problem is starting to drive me crazy... granted it is a short trip.

I would check network settings on those computers, it is possible that there may be some corruption in the TCP/IP stack, I'd uninstall and then reinstall both the TCP/IP protocol and File and Print sharing in the computers that aren't responding to NetBIOS names.

are the other computers Xp?

You said 1 is XP Pro and the other 4 are Media Center?

Okay, let's start with the very basics.

Router:
- Is it a DHCP Server?
- Are there any port restrictions set?

PCs:
- Make sure none have the same machine name.
- Make sure none have static IP addresses set that conflict
- You said they can all ping each other, correct? This means that basic TCP/IP is running, which is good.
- Double check that all firewalls are disabled
- When you browse the workgroup, do you see all the computers?
- Can you connect directyl to a shared drive, ie: \\Servername\share in Explorer?
- Are they all set to use the same WINS server?

If none of this helps, then do wht Gzim suggested. Completely uninstall the Network card and all the associated drivers and then re-boot and let windows find the hardware and install the default drivers with default settings.

Router is runnig as a DHCP server and I am not sure if there are any restrictions, I have to get hold of the ISP and find out from them... its a cisco 1700 I think, also got to ask them if they have it set to let a vpn through.

1 is media center, 3 are pro and one is server 2k3. The problem is with one of the xp pro's and the media center not talking to the other 3 systems.

all the PC's have different names
all systems are DHCP
when ntwork is browsed from the 2 problem computers you get an access denied message when you try to view a list of machines in the workgroup.
when you try to connect directly to the share\server you get an error message.
I don't believe the router is doing any wins stuff and I know the server isn't

Removal of the TCP stuff was next on my list. I have just been so run down from normal work that finding time to devote to this persons network is putting me off my game. That and I can only really work on it when this place is closed, and by that time the owners want to leave.

Oh well this is what they get for not having me do the setup/work from the start.

Thanks for all the help guys, now it is time to go and

Quote: Originally Posted by DickNervous You said 1 is XP Pro and the other 4 are Media Center? Okay, let's start with the very basics. Router: - Is it a DHCP Server? - Are there any port restrictions set? PCs: - Make sure none have the same machine name. - Make sure none have static IP addresses set that conflict - You said they can all ping each other, correct? This means that basic TCP/IP is running, which is good. - Double check that all firewalls are disabled - When you browse the workgroup, do you see all the computers? - Can you connect directyl to a shared drive, ie: \\Servername\share in Explorer? - Are they all set to use the same WINS server? If none of this helps, then do wht Gzim suggested. Completely uninstall the Network card and all the associated drivers and then re-boot and let windows find the hardware and install the default drivers with default settings.

I assume all workstations are authenticating to the domain via the 2003 server?

Are the two problem children logging on locally, or to the network?

U might just need a longer more unique name for the computers some times it's the problem.

Quote: Originally Posted by joecoin I assume all workstations are authenticating to the domain via the 2003 server? Are the two problem children logging on locally, or to the network?

No domain is in place, just a workgroup, although I am thinking of changing them over to a domain to give them added security. I hate cleaning up someone else's mess, especially after they came to me to spec out the server in the first place. Also for some reason the server is set up for terminal server, as well as licensing per server with 5 license as opposed to per seat.

Annoying part is that they used to work just fine.

Quote: Originally Posted by kardiacc No domain is in place, just a workgroup, although I am thinking of changing them over to a domain to give them added security. I hate cleaning up someone else's mess, especially after they came to me to spec out the server in the first place. Also for some reason the server is set up for terminal server, as well as licensing per server with 5 license as opposed to per seat. Annoying part is that they used to work just fine.

Seems like whoever configured this was less than qualified. I would setup a domain, but that's just me.

Have you entered the DNS numbers directly into the network properties?

Also, I have seen XP firewall prevent things from happening EVEN WHEN IT IS TURNED OFF. Enable it , then disable it again.

Good luck.

Sorry for the lack up update. I did finally get the systems to see each other and the rest of the network, although I'm not fully happy with the way it worked out.

I ended up putting a line in the hosts file telling the system where to find the server and boom... works like a charm.

Oh and the problem with setting it up as a domain is that the laptop running media center would be unable to join the domain since that release( and I think all releases) of Media center Edition don't have domain support.

I thought Media Centers Pc's Are not to network friendly.

I'm pretty sure that Server 2K3 systems need static IP's to work correctly...

Well...I don't know if it NEEDS a static IP, but you sure as hell want one, unless you have set DHCP IPs to MAC addresses on router...and even then...