Question Locked

Cannot find network path

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am installing SBS 2003 R2, for a client with three xp client computers in an AD structure.

As far as I can see I have DHCP and DNS configured properly, have the computers and users added with the correct group permissions and local/profile directories created and shared.

Network configuration is as such: DSL Modem connected to one port of the server, Netgear wireless router on the other port with all three clients wired.

I can ping self/domain/internet via ip address or FQDN, I have full internet functionality and the client machines will connect & share correctly in a simple workgroup.

When I go to join the domain, the xp clients accept the domain ID, user and password, then it returns a message "Cannot find the network path" I have read large numbers of threads on this site and others and am still at a loss. I assume it is some small item I haven't configured correctly or overlooked. I have tried with and without firewalls, and even went as far as to open up 1-65k on the router in desperation.

Any ideas would be greatly appreciated.

Brian Linger
Owner
ACSS

8 replies

by oh smeg

At a guess I would say that not only is it not needed where it is but it's preventing the Server seeing the Clients as that is what a Router is supposed to do.

I think that you'll also find that this unit is providing the DHCP and so on as well to the clients.

What you need to do is move the router between the Modem and Server and fit a Hub/Switch between the Server and Clients.

Col

by brian

In this case, both the adsl modem and router are not running dhcp. That is of course enabled by default on both units and the first thing I disabled. DHCP and DNS are handled by the server and pass all tests I can think to toss at them. The IP's are being assinged as I have set in the scope to all objects (router and modem included) and allow both devices to serve their purpose.

I am able to ping loopback/local network nodes/internet by name and number from all machines including the server.

2003 SBS will accept the domain, user + password from the clients. Just to be sure it was actually listening I typed all of them in wrong a few times to make sure I got invalid domain, user/password from the server. Correct entries produce a pause and that wonderful cannot find network path error. Similar message using web interface connect. http://ConnectComputer........

The server did push the client packages to the clients and created the __sbs_netsetup_ account... I know I have connectivity.

by brian

Would love to get rid of it, but this client doesn't want to budget a proper switch, and I really can't afford to buy him one as a gift :) I have read many threads on sites of users getting this type of router to function, and have followed the instructions that have merit on port forwarding and the like. Of course it would appear between the AD setup or the router I have missed something....

by ic-it

You may want to think about a static IP for the Router.
How are you joining the computers? With your credentials or the users? Do those credentials have permissions to join objects?

by brian

The router has a static IP of 192.168.16.1, the modem is static @ 192.168.1.1, server adapters are 16.0, and 1.0 respectivley. Nodes are 16.2 - 4 at this time.

I created two containers for the users, companyname employees, and companyname managment, I have joined employees to the shares for the home & profile shares, and domain users, managment to home & profile shares, domain users, and domain admins, I plan on refining this a little when I can get them to join. Have tried joining users from both groups.

I get the gut feeling that it is something really small I am missing/forgetting. I haven't set up a 2003 SBS AD anywhere but in a lab or at home for "fun", I have set up several 2000 domains succesfully for clients in the past.

Thanks for the suggestions, I am sure one of these is going to make me feel a little silly and solve it! :)

~Brian

by ic-it

Set the servers NICs to something other than 0. that normally indicates the network.
Try 192.168.16.2 and 192.168.1.2
Set your scope beyond that if using DHCP.

by brian

They were actually .1's as they should be I was zombified when I typed it. Oddly enough the solution was simple, if time consuming, I blew out the domain and reinstalled, must have done something wrong the first time I didn't repeat the second. Some little bonehead item... who knows, runs great now, thanx for the suggestions.

~brian

This discussion is closed to new replies.