networking with xp pro and home xp

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hey this is my first time posting on this board. I have this problem it
started back since last weekend and I cant find a way to fix this I hope you
guys can help.

I have two machines one is xp pro and the other is home xp

my xp pro machine can access my home machine no problem but my home machine
cant gain access into my xp pro machine.

I do have all the correct ways for making a workgroup through the networking
wizard.

I hope i can find a way or im going bald fast lol
thanks
brad moore
 
"brad said:
Hey this is my first time posting on this board. I have this problem it
started back since last weekend and I cant find a way to fix this I hope you
guys can help.

I have two machines one is xp pro and the other is home xp

my xp pro machine can access my home machine no problem but my home machine
cant gain access into my xp pro machine.

I do have all the correct ways for making a workgroup through the networking
wizard.

I hope i can find a way or im going bald fast lol
thanks
brad moore

This should help you get everything working:

1. If the computers run the original or SP1 versions of Windows XP,
disable XP's built-in Internet Connection Firewall on local area
network connections -- it's for use only on a direct modem connection
to the Internet. If they run SP2, enable the exception for file and
printer sharing in the Windows Firewall. Disable and un-install all
other firewall programs while troubleshooting. When un-installing a
firewall program, use the un-install procedure provided by the
manufacturer . Don't use Control Panel | Add or Remove Programs,
which might not completely un-install it.

For more information, see:

Windows XP Internet Connection Firewall
http://www.practicallynetworked.com/sharing/xp/ic_firewall.htm

2. Use only one protocol for File and Printer Sharing. If the network
needs more than one protocol, unbind File and Printer Sharing from all
but one of them. Details here:

Windows XP Network Protocols
http://www.practicallynetworked.com/sharing/xp/network_protocols.htm

3. Make sure that NetBIOS over TCP/IP is enabled on all computers.
Details here:

Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/sharing/troubleshoot/netbt.htm

4. Run "ipconfig /all" on XP and look at the "Node Type" at the
beginning of the output. If it says "Peer-to-Peer" (which should
actually be "Point-to-Point") that's the problem. It means that the
computer only uses a WINS server, which isn't available on a
peer-to-peer network, for NetBIOS name resolution.

If that's the case, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and delete these values if they're present:

NodeType
DhcpNodeType

Reboot, then try network access again.

If that doesn't fix it, open that registry key again, create a DWORD
value called "NodeType", and set it to 1 for "Broadcast" or 4 for
"Mixed".

For details, see these Microsoft Knowledge Base articles:

Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
I have tried everything on this list you gave me steve. I can ping both
machines, the only thing that gets me is

the error says this \\Cypher is not accessible. You might have permission to
use this network resource. Contact your server admin

access denied.

Thanks
 
On Sat, 20 Nov 2004 01:45:01 -0800, "brad moore" <brad
Hey this is my first time posting on this board. I have this problem it
started back since last weekend and I cant find a way to fix this I hope you
guys can help.

I have two machines one is xp pro and the other is home xp

my xp pro machine can access my home machine no problem but my home machine
cant gain access into my xp pro machine.

I do have all the correct ways for making a workgroup through the networking
wizard.

I hope i can find a way or im going bald fast lol
thanks
brad moore

Brad,

Make sure the browser service is running on one computer. Control Panel -
Administrative Tools - Services. Verify that the Computer Browser, and the
TCP/IP NetBIOS Helper, services both show with Status = Started.

On the XP Pro computer, check to see if Simple File Sharing (Control Panel -
Folder Options - View - Advanced settings) is enabled or disabled. With XP Home
and Pro together, you need to have SFS enabled on the XP Pro computer.

On XP Home, and on XP Pro with Simple File Sharing enabled, make sure that the
Guest account is enabled, on each computer. Enable Guest with Start - Run -
"cmd", then type "net user guest /active:yes" in the command window.

On XP Pro, if you're going to use Guest authentication, check your Local
Security Policy (Control Panel - Administrative Tools) - User Rights Assignment,
on the XP Pro computer, and look at "Deny access to this computer from the
network". Make sure Guest is not in the list.
 
Thanks Chuck I did try that but I get the same resault no access

on there is one thing that I dont worked and its the net user
guest/active:yes cmd, so am i suspose to put the xp home computer name as
guest or just leave it as guest. Then i get a menu of stuff that i dont know
much about.

Sorry im a newbie

Brad
 
Thanks Chuck I did try that but I get the same resault no access

on there is one thing that I dont worked and its the net user
guest/active:yes cmd, so am i suspose to put the xp home computer name as
guest or just leave it as guest. Then i get a menu of stuff that i dont know
much about.

Sorry im a newbie

Brad

Brad,

We were all newbies at one time. Don't sweat it.

Type exactly "net user guest /active:yes" in the command window.

I'm already bald - too late for me. But I'll try and help you out so maybe you
can fix things before you get there. ;-]

Provide ipconfig information for each computer, so we know what to look at next.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.
 
okay here is the info you are looking for starting with the xp pro machine. I
just uninstalled sp2 but if i need it back I can reinstall it.

Windows IP Configuration



Host Name . . . . . . . . . . . . : OGGY

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : Yes

DNS Suffix Search List. . . . . . : gateway.2wire.net



Ethernet adapter Diabloii:



Connection-specific DNS Suffix . : gateway.2wire.net

Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-0C-76-B4-FB-DA

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.1.2

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.1

Lease Obtained. . . . . . . . . . : Tuesday, November 16, 2004
5:40:04 PM

Lease Expires . . . . . . . . . . : Friday, November 26, 2004
5:40:04 PM


now for the home xp machine "it still has sp2 on it"


Host Name PHOTO2DJ
PRIMARY Dns Suffix
node type unknown
ip routing enabled no
wins proxy enabled no

ehternet adapter local aea connection 2 "first one is disabled"
connection-specific dns suffix gateway.2wire.net
description compaq nc3121 fast ethernet nic
physical address 00-08-c7-6b-40-93
dhcp enabled no
ip address 192.168.1.4.
subnet mask 255.255.255.0
defaualt gateway 192.168.1.1

I had to hand type the last one.

thanks
brad







Chuck said:
Thanks Chuck I did try that but I get the same resault no access

on there is one thing that I dont worked and its the net user
guest/active:yes cmd, so am i suspose to put the xp home computer name as
guest or just leave it as guest. Then i get a menu of stuff that i dont know
much about.

Sorry im a newbie

Brad

Brad,

We were all newbies at one time. Don't sweat it.

Type exactly "net user guest /active:yes" in the command window.

I'm already bald - too late for me. But I'll try and help you out so maybe you
can fix things before you get there. ;-]

Provide ipconfig information for each computer, so we know what to look at next.
Start - Run - "cmd". Type "ipconfig /all >c:\ipconfig.txt" into the command
window - Open c:\ipconfig.txt in Notepad, make sure that Format - Word Wrap is
NOT checked!, copy and paste entire contents into your next post. Identify
operating system (by name, version, and SP level) with each ipconfig listing.
 
okay here is the info you are looking for starting with the xp pro machine. I
just uninstalled sp2 but if i need it back I can reinstall it.

<SNIP>

Brad,

OK, let's do some standard testing.

Take the following code (everything inside the "#####"). (Did I get the names
and ip addresses right)?

Copy the code, precisely as it is keyed, into Notepad. Ensure that Format -
Word Wrap is not checked.
Save the file as "cdiag.cmd", as type "All Files", into the root folder "C:\".
Run it by Start - Run - "c:\cdiag".
Wait patiently.
When Notepad opens up displaying c:\cdiag.txt, first check Format and ensure
that Word Wrap is NOT checked! Then, copy the entire contents (Ctrl-A Ctrl-C)
and paste (Ctrl-V) into your next post.

Do this from both computers, please.

#####

@echo off
set FullTargets=OGGY 192.168.1.2 PHOTO2DJ 192.168.1.4
set PingTargets=127.0.0.1 192.168.1.1
Set Version=1.04
@echo CDiagnosis %Version% >c:\cdiag.txt
@echo Start diagnosis for %computername% (Targets %FullTargets%) >>c:\cdiag.txt
for %%a in (%FullTargets% %PingTargets%) do (
@echo. >>c:\cdiag.txt
@echo Target %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
ping %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
@echo net view %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
net view %%a >>c:\cdiag.txt
@echo. >>c:\cdiag.txt
)
@echo End diagnosis for %computername% >>c:\cdiag.txt
notepad c:\cdiag.txt
:EOF

#####
 
CDiagnosis 1.04
Start diagnosis for CYPHER (Targets CYPHER 192.168.1.3 PHOTO2DJ 192.168.1.4)

Target CYPHER

ping CYPHER



Pinging CYPHER [192.168.1.3] with 32 bytes of data:



Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


net view CYPHER

Shared resources at CYPHER

cypher game

Share name Type Used as Comment

-------------------------------------------------------------------------------
F Disk
Printer Print hp deskjet 845c
The command completed successfully.



Target 192.168.1.3

ping 192.168.1.3



Pinging 192.168.1.3 with 32 bytes of data:



Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128

Reply from 192.168.1.3: bytes=32 time<1ms TTL=128



Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


net view 192.168.1.3

Shared resources at 192.168.1.3

cypher game

Share name Type Used as Comment

-------------------------------------------------------------------------------
F Disk
Printer Print hp deskjet 845c
The command completed successfully.



Target PHOTO2DJ

ping PHOTO2DJ



Pinging PHOTO2DJ.gateway.2wire.net [172.16.1.33] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 172.16.1.33:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


net view PHOTO2DJ

Shared resources at PHOTO2DJ



Share name Type Used as Comment

-------------------------------------------------------------------------------
Printer Print hp psc 2100 series
SharedDocs Disk
The command completed successfully.



Target 192.168.1.4

ping 192.168.1.4



Pinging 192.168.1.4 with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 192.168.1.4:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),


net view 192.168.1.4



Target 127.0.0.1

ping 127.0.0.1



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128

Reply from 127.0.0.1: bytes=32 time<1ms TTL=128



Ping statistics for 127.0.0.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


net view 127.0.0.1

Shared resources at 127.0.0.1

cypher game

here you go
 
CDiagnosis 1.04
Start diagnosis for CYPHER (Targets CYPHER 192.168.1.3 PHOTO2DJ 192.168.1.4)

Target CYPHER

ping CYPHER
net view 127.0.0.1

Shared resources at 127.0.0.1

cypher game

here you go

Brad,

That's a start, but just a start.

My testing is methodical, and works best with complete input.

Your previous set of IPConfigs identified TWO computers - OGGY and PHOTO2DJ.
You apparently have a THIRD computer CYPHER. Looking for your problem will be a
lot easier with diagnostics from all three computers. And it would be good to
have an ipconfig for CYPHER as a reference too.

Also, the diagnostic report for CYPHER is not complete. I explicitly include
"Start" and "End" records in the report, to guard against trying to work from
incomplete reports.

I'll see what clues present themselves in the diagnostic from CYPHER, but we
have the best chance of identifying your problem if you can get a complete
report from CYPHER, and reports from OGGY and PHOTO2DJ too. And if you can
target all 3 computers in each test (ie list all 3 computers and ip addresses in
FullTargets), that is a good idea too.
 
Back
Top