XP Home PC hardwired to router and XP Pro Laptop wireless through 2Wire router...

I am having some problems networking my pc and laptop wirelessly.

The PC has Windows XP Home (SP2) hardwired to the router and the Laptop
has Win XP Pro with a Belkin wireless card. I am using a BT (2Wire
1800hg) router with a built in internet firewall.

The PC and the laptop have no firewalls active on them.

The PC can see the laptop in the workgroup, but cannot open it
(\\LaptopName is unaccessible > > The network path was not found).

The laptop cannot access the workgroup (\\NetworkName is not accessible
> > The list of servers on this workgroup is not currently available).

Both can access the internet through the router and both are showing as
connected in the 2Wire configuration utility (not much use IMO).

The laptop can ping the PC but cannot access any of the shares.

The PC cannot ping the laptop or access any of the shares.

Any ideas would be greatly appreciated.

TIA.
Paul

"phelyer" <(E-Mail Removed)> wrote in news:1126892774.786860.263540
@o13g2000cwo.googlegroups.com:

> I am having some problems networking my pc and laptop wirelessly.
>
> The PC has Windows XP Home (SP2) hardwired to the router and the Laptop
> has Win XP Pro with a Belkin wireless card. I am using a BT (2Wire
> 1800hg) router with a built in internet firewall.
>
> The PC and the laptop have no firewalls active on them.
>
> The PC can see the laptop in the workgroup, but cannot open it
> (\\LaptopName is unaccessible > > The network path was not found).
>
> The laptop cannot access the workgroup (\\NetworkName is not accessible
>> > The list of servers on this workgroup is not currently available).
>
> Both can access the internet through the router and both are showing as
> connected in the 2Wire configuration utility (not much use IMO).
>
> The laptop can ping the PC but cannot access any of the shares.
>
> The PC cannot ping the laptop or access any of the shares.
>
> Any ideas would be greatly appreciated.
>
> TIA.
> Paul
>
>

It usually comes down to the protocols being used on the NIC's.

I run with the following:

1) MS File and Print sharing
2) Networking for MS networks
3) Internet protocol TCP/IP
4) Everything else is removed from all NIC's

That worked for me on Win 2K Pro machine and now they are XP Pro machines
wired and wireless NIC(s).

You can also use MS NWLINK which I used before the above solution was
used to allow wire and wireless machines to share resounces.

Long version

http://www.microsoft.com/resources/d.../all/reskit/en
-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-
us/prch_cnn_lafg.asp

Short version

http://tinyurl.com/cufk7

When I was using MS NWlink, I was using IPsec to protect the NetBios
NWLink is using behind the router on the Windows Networking ports. It's
on the XP O/S too.

http://www.petri.co.il/block_ping_tr...with_ipsec.htm

The implentation of the AnalogX SecPol rules will give you the protection
on the LAN machines and the Windows networking ports automatically when
implemeted. However, the AnalogX rules will block file dowanload using
the High ports > 1024 so you either diable IPsec or you set the ruuls to
open the prticular High port that is needed, which you can use Active
Ports (free) to determine what ports are being used. You learn how to set
the rules by looking at other AnalogX rules.

http://www.analogx.com/contents/articles/ipsec.htm
http://support.microsoft.com/?id=813878

I worked with a guy who has two XP pro machines using a wired Linksys
router and the machines would not network even using the above setup on
the NIC's. He implemented MS NWlink and never looked back.

Duane

Try to install NetBEUI protocol on both machines.
Seems XP home needs that so fa unsupoported protocol to work.
Tardus
===========================
"phelyer" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>I am having some problems networking my pc and laptop wirelessly.
>
> The PC has Windows XP Home (SP2) hardwired to the router and the Laptop
> has Win XP Pro with a Belkin wireless card. I am using a BT (2Wire
> 1800hg) router with a built in internet firewall.
>
> The PC and the laptop have no firewalls active on them.
>
> The PC can see the laptop in the workgroup, but cannot open it
> (\\LaptopName is unaccessible > > The network path was not found).
>
> The laptop cannot access the workgroup (\\NetworkName is not accessible
>> > The list of servers on this workgroup is not currently available).
>
> Both can access the internet through the router and both are showing as
> connected in the 2Wire configuration utility (not much use IMO).
>
> The laptop can ping the PC but cannot access any of the shares.
>
> The PC cannot ping the laptop or access any of the shares.
>
> Any ideas would be greatly appreciated.
>
> TIA.
> Paul
>

> When I was using MS NWlink, I was using IPsec to protect the NetBios
> NWLink is using behind the router on the Windows Networking ports. It's
> on the XP O/S too.

Explain how you would use IPSec which is for IP hence "IP Security"
policies to work with NWLink which is Microsofts implementation of the
Xerox (and then later Novell) Internetwork Packet Exchange protocol
(IPX).

FWIW, NWlink doesn't use NetBIOS rather NetBIOS sits on top of NWlink to
provide a programming interface rather than use the sockets programming
interface offered by NWlink.

Or is that not what you're saying above?

David Taylor <(E-Mail Removed)> wrote in
news:(E-Mail Removed) d.com:

>> When I was using MS NWlink, I was using IPsec to protect the NetBios
>> NWLink is using behind the router on the Windows Networking ports.
It's
>> on the XP O/S too.
>
> Explain how you would use IPSec which is for IP hence "IP Security"
> policies to work with NWLink which is Microsofts implementation of the
> Xerox (and then later Novell) Internetwork Packet Exchange protocol
> (IPX).

Why don't you read the AnalogX IPsec link or better yet implement the
AnalogX Secpol on a machine and look at the rules and figure it out for
yourself. Why do I have to explain things to you?

>
> FWIW, NWlink doesn't use NetBIOS rather NetBIOS sits on top of NWlink
to
> provide a programming interface rather than use the sockets programming
> interface offered by NWlink.
>
> Or is that not what you're saying above?

Well David I am no guru like you seem to pretent that you are. All I know
is the NWlink when installed, additinal things are installed with it such
as NetBios i guess.

http://www.securiteam.com/windowsntf...JP0115B5S.html
http://www.winguides.com/security/display.php/127/

AnalogX's implmentaion of the Secpol rules futher protects the machines
in a LAN situation. You want to know how it's doing it implement the
thing and take a look for yourself.

If you want to take it any futher than that, it's your problem not mine.

I really am tired of you and your lurking Pamper shit.

I really am tired of you David you are worst than a two year old running
around in a Pamper. And I don't want to hear your BS about keep it
technical, because technically, you can stick it right up your ass.

> Explain how you would use IPSec which is for IP hence "IP Security"
> policies to work with NWLink which is Microsofts implementation of the
> Xerox (and then later Novell) Internetwork Packet Exchange protocol
> (IPX).
>

And one other thing you ass wipe, I was working on the Novell server
platform back in 1996 through 1999 using LWLink on Win 3.x or/and DOS 6.22,
Win 9'x and Win NT 4 workstations and know what NWlink is about before the
facility went to all MS Win 2K servers and workstations in 1999. I didn't
need a damn history lesson from you on it.

My last parting shot as I have to hit the door running in the AM to make
that 2.5 hr trip to O'Hare International Airport to catch a flight to Reno,
NV and work a contract to convert all Web, Windows Desktop and Windows
Server applications using Win XP Pro and Win 2k3 and IIS for their ASP 3.0
using JavaScript and ASPscript and Visual Studio 6 business solutions and
convert them all to ASP and VS .NET business solutions. And they are paying
some long $$$$$$$ to do it.

I don't give a rat ass if these links are concering Win 2K, because XP
Pro/Home and Win 2K3 are NT base O/S(s) and IPsec runs on them and I have
implemeted the AnalogX SecPol rules at least on Win 2K and XP Pro and I know
the rules protect, along with using MS NWlink myself on the Win2K machines.
in a wireless where the BFW11S4 v1 router would not allow a connection
between a wire and wireless machine due to WEB being enabled and the NetBeui
on the NIC's. Little did I know David that it would have worked with Netbeui
being removed as I was told that NetBeui was not a routable protocol and
that was the problem. But little did I know about it until such time that I
converted the machines to XP pro with NetBeui not being there and it worked.
So most likely it would have worked on Win 2K too had I just left NetBeui
off and not went to NWlink.

But hey, I am not a fuclking guru like you and this old dog is still
learning and I have been programming since 1980 on the IBM mainframes and
client server platforms and woking in the IT field since 1971 when Apple was
in a wodden box.

> http://www.securiteam.com/windowsntf...JP0115B5S.html
> http://www.winguides.com/security/display.php/127/

David, you are an absolute fucking ass hole.

I'll continue to deal with your lunatic ass from Reno.

Later!

Duane

That is WEP not WEB as I don't want you going off with a Pamper pissing on
me.

"Duane Arnold" <(E-Mail Removed)> wrote in message
news:I1MWe.359516$xm3.58880@attbi_s21...
> My last parting shot as I have to hit the door running in the AM to make
> that 2.5 hr trip to O'Hare International Airport to catch a flight to
> Reno, NV and work a contract to convert all Web, Windows Desktop and
> Windows Server applications using Win XP Pro and Win 2k3 and IIS for their
> ASP 3.0 using JavaScript and ASPscript and Visual Studio 6 business
> solutions and convert them all to ASP and VS .NET business solutions. And
> they are paying some long $$$$$$$ to do it.
>
> I don't give a rat ass if these links are concering Win 2K, because XP
> Pro/Home and Win 2K3 are NT base O/S(s) and IPsec runs on them and I have
> implemeted the AnalogX SecPol rules at least on Win 2K and XP Pro and I
> know the rules protect, along with using MS NWlink myself on the Win2K
> machines. in a wireless where the BFW11S4 v1 router would not allow a
> connection between a wire and wireless machine due to WEB being enabled
> and the NetBeui on the NIC's. Little did I know David that it would have
> worked with Netbeui being removed as I was told that NetBeui was not a
> routable protocol and that was the problem. But little did I know about it
> until such time that I converted the machines to XP pro with NetBeui not
> being there and it worked. So most likely it would have worked on Win 2K
> too had I just left NetBeui off and not went to NWlink.
>
> But hey, I am not a fuclking guru like you and this old dog is still
> learning and I have been programming since 1980 on the IBM mainframes and
> client server platforms and woking in the IT field since 1971 when Apple
> was in a wodden box.
>
>> http://www.securiteam.com/windowsntf...JP0115B5S.html
>> http://www.winguides.com/security/display.php/127/
>
> David, you are an absolute fucking ass hole.
>
> I'll continue to deal with your lunatic ass from Reno.
>
> Later!
>
> Duane
>

On 16 Sep 2005 10:46:14 -0700, "phelyer" <(E-Mail Removed)> wrote:

>The PC and the laptop have no firewalls active on them.

OK, that eliminates the obvious problem.

>The PC can see the laptop in the workgroup, but cannot open it
>(\\LaptopName is unaccessible > > The network path was not found).

Try it by IP address instead:
Start -> Run ->
\\192.168.1.xxx
It should show the same directory listing as using the NETBIOS name.
This is a common problem when the Windoze Browser Election kludge
screws up. Doing it by IP address directly bypasses the NETBIOS to IP
name resolution pretzel.

>The laptop cannot access the workgroup (\\NetworkName is not accessible
>> > The list of servers on this workgroup is not currently available).

Ummmm, try it like this:
NET VIEW /WORKGROUP:workgroup_name

>Both can access the internet through the router and both are showing as
>connected in the 2Wire configuration utility (not much use IMO).

Can I assume that both machines have IP addresses assigned by the DHCP
server inside the 2wire router? If either is statically assigned,
switch it to DCHP (server assigned IP, gateway, netmask, DNS).

>The laptop can ping the PC but cannot access any of the shares.
>The PC cannot ping the laptop or access any of the shares.

OK, this is bad. I had exactly the same problem this week. New
laptop was acting strange. Sometimes would not get a DHCP assigned IP
on reboot. Other machine was also doing weird things like hanging in
the middle of downloads. One machine could ping the other, but not
the reverse. Both had no difficulty connecting to the internet.
Both went to a common 8 port ethernet switch.

After tinkering with the network settings, I started to suspect the
hardware. I eventually found that BOTH ethernet cables were wired
wrong with split pairs. Of course, I replaced the cables one at a
time so finding this took a bit longer than usual. After replacing
the cables, they could ping each other.

So, start with replacing the cables. Use ping to do the testing as
it's the fastest and is a fundamental requirement for connectivity.
Use:
IPCONFIG
to verify that the IP addresses are what you think they are and have
not changed during the testing.

It'a also good form to have duplicated accounts on both machines. If
you get an error message where Windoze demands a password to open a
share, it's probably due to the lack of a common user account.

Also, make sure that the workgroup name is the same on both machines.
Right click on My Computah. Select System Name.


--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831.336.2558 voice Skype: JeffLiebermann
# http://www.LearnByDestroying.com AE6KS
# http://802.11junk.com
# (E-Mail Removed)
# (E-Mail Removed)