Jump to content

[Help] Network is broke :(


Recommended Posts

Posted

Hey,

I am having a problem with computers being able to access each other over a wireless network...

Computer A - WXP Pro, nlite (custom install), autopatchered

Computer B - WXP Pro standard

Computer C - WXP Pro standard, autopachered

Now Computer A can access Computer B and see its shared files and that but Computer A won't let Computer B see its shared files, or the computer for that matter. Computer A connects to the internet through Computer B fine :S. Now Computer C can share its connection with Computer A but neither can access shared files. Computer C can access Computer B but Computer B can't access Computer C.

The network is setup like so:

Router---Computer C

'---Computer B

The router is not wireless, the wireless part is when Computer A connects to Computer C or Computer B, depends which one I plug in the usb wireless nic.

I have a feeling its something to do with the registry/services/advanced network settings (like WINS TCP/IP etc...) cause I've done everything right by windows :S

Hopefully theres enough info here cause this is all I know atm. I've tried google and its a bunch of dead ends . Could something I removed from nlite have caused this?, I'll post my nlite config if so...

Thanks in advance,

nerd

Title edited -- Please, use [TAGS] in your topic's title.

Please follow XP Forum Rules from now on.

--Sonic


Posted

I typically don't bother surfing to a network destination, I've found that Windows' ability to find networked devices are a bit weak...

Memorize your computer name and just navigate to it directly...

So in My Comter's address bar we would type "\\ComputerB\Share\" and it'd take us directly to the thing, rather than waiting for XP to find it, you're telling it "It exists, now to there"

Posted

Hey,

Yeah, if I do that from Computer B to Computer C I get an error message saying that I do not have network permission to access that resource :S yet its all set up to allow it... Computer C can be access by either of them though...

Nerd

Posted (edited)

The first thing I'd check are the share & file permissions on the directory you want to be public.

Do all 3 machines have a common username & PW?

@nakatomi2010

agree most strongly-UNC is way cool! :thumbup

Edited by Must4ng
Posted (edited)

He doesnt -need- a common username password for all pcs, merely the knowledge of one on each. When mapping the drives he should use the "connect using a different username and password" option - in the following format (for workgroups):

username: "<other computer name>\<other computer's local user>"

password: "<password of the user account on the other computer>"

also NTFS and share-level permission should be set for the user account that will be used to access the share.

to ensure connectivity (assuming most settings are windows default and the network hardware is fine):

-for the small network use statically assigned IPs instead of DHCP.

-check that netbios over TCPIP is enabled in advanced properties of the TCPIP component for the networking adapter used.

-windows firewall (if used) has exceptions for windows file and printer sharing.

-in an environment lacking a proper DNS server (no a router doesnt count) add entries to the hosts file (%windir%\system32\drivers\etc\hosts) for the other hosts you want to connect to.

Edit: furthermore, administrative shares could be mapped for each other host - using the UNC path \\<computer name>\<drive letter>$ which allows browsing of the roots of volumes of other machines - however as the name implies an administrative account's credentials must be supplied when mapping the drive.

Edited by ironfist241
Posted
Hey,

Yeah, if I do that from Computer B to Computer C I get an error message saying that I do not have network permission to access that resource :S yet its all set up to allow it... Computer C can be access by either of them though...

Nerd

This error doesn't necessarilly have anything to do with permissions, you will see the same error message if the computer you are trying to access can't be found on the network.

WHAT HAPPENS WHEN YOU DISABLE THE ANTI-VIRUS OR WINDOWS FIREWALL?

Windows default firewall can prevent network shares from being accessible. Try turning it off (if you haven't already), and see if that corrects the problem.

Posted (edited)

Hey,

On both wireless adapters (Computer A,C) I have enabled NetBios over TCP/IP and gave them static IP address. They still have connectivity (Computer A can still get on the internet through Computer B) though when I type the computer name of either I get:

\\computername is not accessible. You might not have the permission to use this network resource. Contact the admini..... Access Denied

I've also turned simple filesharing off and checked the permissions, both have Everyone in the list with the correct boxes ticked. Firewall is also off...

I removed administrative shares on my nlite install, could that have caused this?

in an environment lacking a proper DNS server (no a router doesnt count) add entries to the hosts file (%windir%\system32\drivers\etc\hosts) for the other hosts you want to connect to.
I don't understand this :S

nerd

P.S. These are my nlite and registry cfg's

http://nerdco.nerdtech.ws/Temp

Edited by nerdco
Posted

When you're browsing the network using UNC paths you need to specify \\computerrname\sharename-just \\computername won't work, e.g. \\P51DMustang\c$ will take you to the root of my gaming boxes' c: drive.

BTW, on the check the simple stuff first premise, I forgot to ask if all computers in the same workgroup?

Vis a Vis the hosts file entries referred to by ironfist241:

just browse to the directory provided and open the file in Notepad.

The hosts file itself will give you the format to use

The host name is the comp you want to connect to, e.g. 10.102.1.125 P51DMustang #Gaming box

@ironfist241

You're correct that common usernames/PW's aren't required-it's just a convenience and lessens the load on my last remaining brain cell. Trying to remember account info on the gaming box, the work box, the wife's comp, the grandkids' box and the guinea pig box got to be a PITA a long time ago.....

they do say memory is the first thing to go... :o

Posted
When you're browsing the network using UNC paths you need to specify \\computerrname\sharename-just \\computername won't work, e.g. \\P51DMustang\c$ will take you to the root of my gaming boxes' c: drive.
This is not correct.

Entering \\computername will contact the target machine, authenticate as either Guest (if simple file sharing is enabled) or with credentials you are prompted for or have used previously in this logon session. Next the target computer responds with the list of resources which are shared (not just those to which you have access based on your credentials, this check is performed when you attempt to access the resource).

Entering \\computername\sharename does the same process but automatically requests access to the specified resource instead of obtaining the list.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...