Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Resolved Question

XP pro workstation can't one server, but can others

Nov 23, 2011 1:21AM PST

Hi,

Well, I have this issue, where one XP pro workstation can not access a server (file server), but can access the rest of the network and the Internet. It seems it's the only workstation that can't access that server, no one else is having any issues with that server.

Help!!!! Please!!!!

Thanks,
George

Discussion is locked

gmak1988 has chosen the best answer to their question. View answer

Best Answer

- Collapse -
Tell more.
Nov 23, 2011 2:42AM PST

Is this a Domain Server?

If not, I wonder if you bumped into the server limit of Windows XP. That's 5 or 10 users tops and could result in a question like yours.
Bob

- Collapse -
Re:
Nov 23, 2011 3:35AM PST

Nope, it's a backup server, that also serves as a file server.

- Collapse -
So it's not a domain or "server" that you can tell more.
Nov 23, 2011 3:43AM PST

Without knowing if it's a domain or such, I can't guess what the issue is. However it could be a business problem such as they need to get their IT staff upgraded. More schooling, seminars and books.
Bob

- Collapse -
Re:
Nov 23, 2011 4:09AM PST

The backup server is running Windows 2003 and DC is running Windows 2008 R2. The backup server is the one that the workstation doesn't see. I can ping any other server on the network, access them, access other shares, etc. The backup server is not the DC server, however it does serve as alternative DNS.

Hope this helps.

George

- Collapse -
The first test.
Nov 23, 2011 4:15AM PST

Ping the backup server by IP address. If that fails we investigate why.

Then again, ping can be disabled on that server. Your IT staff should re-enable it for a test run.

Also, I hope this is Windows Server 2003.

--> After you get PING working we need to discuss the "Network Neighborhood" and how it is unreliable. This is where your IT staffer may need some seasoning. That is, they would know to not rely on that but open a command line to use NET VIEW. And to head off a question, no, this issue was never resolved. I see it happen today on the latest Windows.
Bob

- Collapse -
Re:
Nov 23, 2011 4:36AM PST

It times out. NET VIEW was ran and the PC is on the domain, sorry I thought it was implied that NET VIEW was ran.

- Collapse -
We can't imply much.
Nov 23, 2011 4:41AM PST

Today I encounter new IT staff that has never used the command line. They lack basic TCP/IP skills and would write all the above without use of NET VIEW.

Good luck in resolving the ping timeout. You've nailed why it can't see it. As the details are only given in this discussion, this is all you need to cure.

That is, it is simply a ping issue. We don't worry about anything else till we fix the ping issue.
Bob

- Collapse -
Re: we can't imply much
Nov 29, 2011 12:30AM PST

arp -d * did the trick. Ran it on the server.

- Collapse -
Answer
PING tips.
Nov 23, 2011 5:40AM PST

1. Ping by name.
2. Ping by ip.
3. Examine the hosts file.
4. Turn off any firewall for a test run.