General discussion

Locked

Cannot access W2K server

By daniel ·
We are unable to access or browse our W2K fileserver today across the WAN, although everything was working fine last week. Although the server name appears in Network Neighborhood, when I select the server or attempt to access a mapped drive to that server, the following message appears: \\Fileserver is not accessible. Network path was not found

The fileserver, which is running Windows 2K in an NT domain at our main branch, can be accessed with no problems within the main branch (local network). We are able to successfully ping and trace a route from the remote branches to the fileserver, so it doesn't appear to be a name resolution issue. In addition, all other servers can be accessed from the remote braches, so it doesn't appear to be a routing issue.

We recently replaced the previous NT4 fileserver with a new server running W2K server, and used a 3rd party software NetIQ to migrate the shares and permissions. It has been three weeks since the migration, and everything was working fine. Last week one of our remote locations could not access the fileserver, the next day everything was fine.

Any suggestions,
Dan

This conversation is currently closed to new comments.

13 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by jorge.rivera In reply to Cannot access W2K server

Is needed performa more test..and more info...
Try access using IP Address,, loca and from some branch office.....
The old server name, ip are the than the new server ???

Collapse -

by daniel In reply to

Poster rated this answer.

Collapse -

by Andrew Cooke In reply to Cannot access W2K server

I have had this in the past, sounds like a browser issue. Can you answer each of these points.

1) Can you do start|run \\IPADDRESS
2) nbtstat and ipconfig /flushdns have a few options. nbtstat -c will show you the local PC cache.
3) Can you check the WINS settings and let me know what appears in the database in the square brackets

Collapse -

by daniel In reply to
Collapse -

by abubin In reply to Cannot access W2K server

i am suspecting this to have something to do with DNS server or settings.

Make sure that all your DNS servers are working fine. Did you upgrade your NT domain to w2k domain? If yes, check your AD. Most probably one of your DNS settings is not running correctly. That's why sometimes your WAN access doesn't work. Like when it's DNS cache times out, it switches between DNS servers and one of them doesn't work so you can't access the fileserver.

Hope this helps.

Collapse -

by daniel In reply to

Poster rated this answer.

Collapse -

by jaboy78 In reply to Cannot access W2K server

After restarting the server, it should be ok.
i think the main isuue is that is it the server automatically scan virus by schedule??

That should be the main isuue.

Collapse -

by daniel In reply to

Poster rated this answer.

Collapse -

by Tictag In reply to Cannot access W2K server

My thoughts:
Name resolution has been proven, as has TCP/IP connectivity the one thing that remains to be proven is SMB file sharing.

Try:
1. Check each interface in the connectivity chain to the fileserver for any File and Print Sharing or NetBIOS over TCP/IP disabled adapter interfaces. Especially (if applicable) any RAS interfaces.
2. Check any firewalls preventing ports UDP137 / TCP139 traffic.
3. Capture traffic on both the server and client using Network Monitor
4. Analyse result of NETDIAG tests on client and server.

HTH,
Tictag.

Collapse -

by daniel In reply to

Poster rated this answer.

Back to Windows Forum
13 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums