Re: It's NOT WORKING AGAIN!
From: Keppy (keppy_at_msn.com)
Date: 06/10/04
- Next message: Keppy: "Re: It's NOT WORKING AGAIN!"
- Previous message: John Nivard: "Re: NAT server problems for weeks Who can help??????????"
- Maybe in reply to: Keppy: "It's NOT WORKING AGAIN!"
- Next in thread: Phillip Windell: "Re: It's NOT WORKING AGAIN!"
- Reply: Phillip Windell: "Re: It's NOT WORKING AGAIN!"
- Reply: Phillip Windell: "Re: It's NOT WORKING AGAIN!"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 10 Jun 2004 13:17:45 -0700
"Phillip Windell" <@.> wrote in message
news:%23BMd%23wwTEHA.3368@TK2MSFTNGP11.phx.gbl...
>
> "Keppy" <keppy@msn.com> wrote in message
> news:ONLmkbwTEHA.3528@TK2MSFTNGP12.phx.gbl...
> > When I look in Windows Explorer, Networks, I can see the network name
and
> > this computer under it. I don't list the other computers under the
> network.
> > But If I try to access this computer through the network connection that
I
> > see, I get a "not available, may not have permissions" This is the
> computer
> > I'm on.
> >...............................
> > in the connected computers, yet the tools say I am connected to the
> internet
> > and the network (I can access the internet!)
>
> If you can get on the Net, then the literal network settings of the NIC
are
> correct. The "broadband device" is just a NAT device and NAT is a Layer3
> function, so it doesn't care squat about the rest of your Windows
Networking
> settings.
>
> You might want to have *all* the machines set their network setting to
> "automatic" and let the Broadband Device autoconfigure them using its DHCP
> features, then you will *know* that all machines consistant with each
other.
> Since you only have a Workgroup and no DC you don't have to worry about
> keeping any server with a static address.
ALL my computers are set to auto DHCP
>
> > Originally this computer was set up as the server.
> > I don't know if that is the case anymore.
>
> What to do mean by "was" a server? XP Pro is not a server and it can not
be
> a server.
>
> > They are more like peer to peer in that all the other computers can
> communicate with
> > all four computers equally.
>
> If there is no Domain Controller then you have a Workgroup. Workgroups are
> always "peer-to-peer" and can not ever be anything else.
Great, they're peer to peer, I still can't get one desktop to behave.
>
> > will not see or even communicate with itself via the network connection
in
> > Windows Explorer (this computer is using OS XPpro, another wireless
> desktop
> > is also using PRO, one is using HOME and one MEDIA but all are using XP)
>
> Workgroups depend on these things:
> 1. Regular network settings must be correct and consistant between all
> machines.
They are and they all can share. Even the one that I'm having problems with,
the other computer can share with it.
> 2. Workgroup name must match on all machines
Exactly the same
> 3. File & Print Sharing must be enabled
That's why all the computers are able to share, even with the one computer
I'm having problems with, the other computers can access it's shared drives
and files.
> 4. Something must actually be shared.
I have shared drives, printers and external devices like peerless drives.
All sharing nicely for all machine but one.
> 5. All machines must have duplicate user accounts & passwords.
What does this mean. all machines have only one user and password per
machine and all can share except the one.
> 6. Personal Firewalls on the machines must be disabled or very *carefully*
> configured.
During this attempt to connect this damn computer, I have disabled all
software firewalls AND auto virus scanning.
>
> If these are all correct the check the machine for "spyware".
Have done so with both Ad-aware and Spybot
> First:
> Go to Add-Remove Programs. Remove all non-essential and non-MS related
> "Internet Garbage" (Tool Bars, Search Utilities, and other things the
> programmer was too stupid to even capitalize in the "display name"
> properly). Programs with names in all lower case or all upper case, or
with
> "cryptic" names that don't make sense is a "red flag".
> Second:
> Download, Install, Update, and Run "Ad-Aware" from www.LavasoftUSA.com .
> Remove what it finds.
>
> Clear Temp Internet Files from browser's cache. Leave the browser's cache
> size set to the minimum of 1meg and select "every visit to page". Then
> update and run a full scan with your favorite AV software.
>
All garbage has been removed, no recycled, no temp, no thinging.
Phil, I have tried everything I can fine. I don't have a virus or anything
else that I can find that would create havoc on this computer. As far as I
can see, all the setting on this computer are basically the same as the
other three. I tried removing the network and setting up a fresh network
with a new name and 128WEP. All three computer are now connected to the new
network and sharing nicely. This computer, when I drop down the networks in
Windows Explorer, I see both networks. In my system properties, it shows the
correct new network name, but the same problem. All the other computers can
get on this one, but this one can't get, or even recognize, the others. The
others MUST all be setup correctly, because if it wasn't for this computer,
they're all sharing the cable connection, they are all logged onto the new
network name, I can map drives from any of the three to any of the other
THREE, including this one. This one desktop, it is the only one NOT
wireless, it's connected by a network cable, not that that should have any
affect... unless the problem is with that port on my router EXCEPT, I can
get on the internet, so that probably isn't the case.
Any other ideas? I'll try anything at this point. Did you see all the
responses to your other questions in the previous thread? I did the ipconf
and all the pings and posted everything for you to see.
I had to take a valium last night. I'm the kind of person that doesn't even
like taking asprin unless it's life or death. I am so stressed out. It's not
just that it's a pain to have to go to another computer to get stuff
transfered over for backup from this computer, but the fact that this
problem exists and I can't fix it!
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>
- Next message: Keppy: "Re: It's NOT WORKING AGAIN!"
- Previous message: John Nivard: "Re: NAT server problems for weeks Who can help??????????"
- Maybe in reply to: Keppy: "It's NOT WORKING AGAIN!"
- Next in thread: Phillip Windell: "Re: It's NOT WORKING AGAIN!"
- Reply: Phillip Windell: "Re: It's NOT WORKING AGAIN!"
- Reply: Phillip Windell: "Re: It's NOT WORKING AGAIN!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|