Jump to content
Compatible Support Forums
Sign in to follow this  
BillP

Can't see NT server with XP Pro workstation

Recommended Posts

I recently inherited a NT Server network and am trying to connect to it with Windows XP Pro. The XP box uses static TCP/IP protocol to connect to the internet. Previously I connected to the server as a workgroup using Netbeui, which is also installed on the server.

 

How can I connect to the server?

Can I configure the XP's TCP/IP to see the server or do I have to install another protocol? Would IPX work?

 

Thanks for your assistance

Share this post


Link to post

When you say "see the server", do you mean that you just do not see it listed in Network Neighborhood, or that you can't ping it either? Is NetBIOS over TCP/IP enabled in the TCP/IP properties of the WinXP clients? Are you using DHCP or a static addressing scheme? Lastly, are you using WINS or DNS as a name resolution scheme on your network?

 

Just making sure that NetBIOS over TCP/IP is enabled will usually fix this issue.

Share this post


Link to post
Quote:

When you say "see the server", do you mean that you just do not see it listed in Network Neighborhood, or that you can't ping it either? Is NetBIOS over TCP/IP enabled in the TCP/IP properties of the WinXP clients? Are you using DHCP or a static addressing scheme? Lastly, are you using WINS or DNS as a name resolution scheme on your network?

Just making sure that NetBIOS over TCP/IP is enabled will usually fix this issue.


>>Actually, I need to access files on the server.
>>I believe I enabled NetBios over TCP/IP, but I'll check again.
>>I use static as I have a fixed IP for internet access
>>I inherited this server, how would I check to see if WINS or DNS is enabled?
thanks...

Share this post


Link to post

So it is being listed in Network Neighborhood? You can ping between the clients and server? How familiar are you with NT Server? You can see if the clients are pointing to a WINS box in the TCP/IP properties panel, but the service itself would be running on a NT Server.

Share this post


Link to post

No, network neighborhood on the server and xp box don't see each other, although the xp box sees other systems on the network which have static ip addresses and netbuei installed. Haven't tried ping...will do that today. And, although I have a rudementrary understanding of NT, I am really a novice. The Server, I believe, does not have WINs enabled but has netbeui and tcp/ip protocols.

...Bill

Share this post


Link to post

Enable NetBIOS over TCP/IP on both systems, and you shouldn't need support for NetBEUI on all the XP system (or any of them really) since you will have the NetBIOS name/resource handling riding on TCP/IP.

Share this post


Link to post

umm.... just to make sure, have you checked that the server is on the same subnet as all the other boxes? i.e., do the ip addresses all start with the same numbers?

Share this post


Link to post

Well, I took the cowards way out...I installed netbeui from the Windows XP disk. This was the most expeditious solution as it was a crazy day at work and they didn't want me to take the server down to mess around with IPX or resetting the Server's TCP/IP scheme. I don't think there is much downside using this protocol...this network (NT Server with domain) was created to support 6 systems and I can't figure out what our prior consultant was thinking of...besides his own enrichment. All we use the server for is for file sharing and a couple of network programs that work well on peer-to-peer networks.

 

Once Netbeui was installed all was well...XP box sees the server and other computers on the network.

 

Thanks for your assistance...when I have a chance I will see if I can get the TCP or IPX protocols to work.

 

I much appreciate your assistance.

 

...Bill

Share this post


Link to post

Get away from NetBEUI and don't waste your time with IPX/SPX. Neither of them add value to the network and only add more management headache as well as a taller stack of bindings for the systems to go through. Also, having more protocols makes troubleshooting much more difficult since you can't tell if one protocol is picking up the slack from another that is misconfigured (as in your case).

Share this post


Link to post

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×