Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Linksys router & DSL ok.. but now no network access

Status
Not open for further replies.

qotyebw

Programmer
Aug 24, 2000
103
US
Linksys cable/DSL 4-port router has been installed on the network, and we're online ok.. but now no network access for 3 of 5 users.
"Domain controller for your domain could not be contacted..."

Of course, I did not copy the original IP addresses for those workstations in order to restore the original config... no excuse for that.

Help?

 
Actually, those users do have network access, but have lost access to the network file-server's drives. Find Computer does not locate it.
Did I mention that I'm not very network savy?
 
What kind of server so you have, 2k, NT? Have you run an IPCONFIG from the server? You may need to remap your drives? Matt Wray
CCNA, MCP
mwray77518@yahoo.com
 
These are all NT workstations. 2 of these do not recognize the file server, and cannot seem to map to the drives there. How would I proceed with IPCONFIG? Will look into it...
Thanks.
 
Start-> Run-> cmd. From the command prompt, IPCONFIG /ALL. This will tell you teh IP of your server, and the address of the DHCP server as well. Make sure you server is receiving an IP from the linksys. Then try and ping the other machines. If you can ping, you should be able to map your shares. From your NT clients command, type NET USE /?, and this will tell you the syntax of what you need to do. Post back and let me know... Matt Wray
CCNA, MCP
mwray77518@yahoo.com
 
Just to re-cap & explain a bit better..
There's about 12 NT workstations, all in one domain. Two of these computers cannot access mapped drives on workstation3, which is accessible by all others. Using Find Computer will not detect that workstation (which I refer to as a "fileserver").
On startup, I get the message:
"Domain controller for your domain could not be contacted..."

I'll attempt to follow your instructions on Monday morning, but what's a "NT clients command"?
 
I think he meant, "... from a command prompt on an NT client, type 'NET USE /?' ..."

The Old Man
 
There's a lot of data to transcribe from the ipconfig/all command I'll boil it down:

One computer contains the drives that everyone maps to (let's call it
workstation3).
I can ping workstations1 & 2 from any other computer, except from
workstation3. Workstations1 & 2 can ping all others, except
workstation3. When workstations1 or 2 try to ping workstation3, I get
"request timed out"

workstation1 : 192.168.1.100
workstation2 : 192.168.1.104
workstation3 : 123.123.123.123 (not intended to be used as a
browser/internet use)

All PCs (except for workstation3) have the same default gateway &
DCHP server ip's (192.168.1.1). All subnet masks are 255.255.255.0,
except workstation3 is 255.255.0.0. DHCP is disabled in orkstation3
 
Your problem is the IP address of your file server. Do you have a static IP as described above? CHange it to one in your network range (192.168.1.x, 255.255.255.0). If you don't want it to get to the Net, do not supply a gateway for that machine. Try that and see what happens. And the old man was right, that was what I meant (from the NT clients command prompt)... Matt Wray
CCNA, MCP
mwray77518@yahoo.com
 
Thanks Matt,

I had this issue wrapped up in another discussion group with The Old Man. Of course the adventure continues. Check out June 4.. thread581-284745

With the Linksys router running the DHCP, all is well on all NT computers in the network... except for the one running XP. It's Autoconfiguration seems to prevent DHCP from outside the workstation. Got a registry fix in the works, but i'm not comfy with it...
 
Why not try a static IP for the XP machine. Just make sure it is in the same range as the other machines and with the same gateway. Then try and ping the other machines. If you are unaable to ping, something is bad, cable, jack, etc. Matt Wray
CCNA, MCP
mwray77518@yahoo.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top