Can't get three computers on wireless network to work with each other.

Uncletoad · 11-21-2007, 07:03 PM

I have two identical IBM T42 notebooks on a network at my business, one lives in a dock still using wireless connections for LAN. I have an IBM T42p that travels back and forth between there and home where another T42 lives.

I have Dlink 624 routers at both places. The workgroup name is the same both places. I can ping all the boxes at any place all the time.

Frequently (more often than not) the computers don't see each other.

Can someone point me to a process to troubleshoot this?

I'm attempting to run Quickbooks multiuser mode through the Network and can't get it to work if the boxes don't reliably see each other.

I'm using Windows to configure my wireless connections not IBM's Access Connections.

All three computers at work have fresh images within the last month.

I gave up on my recent image with the T42p and have just finished redoing it again.

Still have the same problems.

Windows XP Pro on all computers. None have ever had problems getting on the internet through the network.

BMR777 · 11-22-2007, 07:31 AM

When you imaged them, did you give them the same image? There might be a slight chance that all of the computers have the same computer name due to the imaging, which can cause confilcts.

Right click on My Computer, select properties and then go to the Computer Name tab. Check that the name is different on all of the PCs. Also make sure no other PCs on the network have the same name. If it is the same, change the computer name to something unique on all computers.

BMR777

Uncletoad · 11-22-2007, 07:57 AM

Names are all different. Usernames are all different. I used the original image format CD's and added the software and files we use but each box is an individual.

johnwill · 11-22-2007, 09:55 AM

Let's see this for each computer when they're all connected to the network.

Start, Run, CMD to open a command prompt:

Type the following two commands:

nbtstat -n

ipconfig /all

Right click in the command window and choose Select All, then hit Enter.
Paste the results in a message here.

If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.

Uncletoad · 11-23-2007, 07:58 AM

From the T42p:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Phil Maneri>nbtstat-n
'nbtstat-n' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Phil Maneri>nbtstat -n

Wireless Network Connection:
Node IpAddress: [192.168.0.112] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
UNCLETOAD <00> UNIQUE Registered
UNCLETOAD <20> UNIQUE Registered
TOAD <00> GROUP Registered
TOAD <1E> GROUP Registered

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

C:\Documents and Settings\Phil Maneri>ipconfig /all

Windows IP Configuration

An internal error occurred: A device attached to the system is not functioning.

Please contact Microsoft Product Support Services for further help.

Additional information: Unknown media status code.

C:\Documents and Settings\Phil Maneri>

And from the second T42:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Fretshop>ntbstat -n
'ntbstat' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Fretshop>nbtstat -n

Wireless Network Connection 2:
Node IpAddress: [192.168.0.111] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
FRETSHOPMAIN <00> UNIQUE Registered
FRETSHOPMAIN <20> UNIQUE Registered
TOAD <00> GROUP Registered
TOAD <1E> GROUP Registered
TOAD <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

C:\Documents and Settings\Fretshop>ipconfig /all

Windows IP Configuration

An internal error occurred: A device attached to the system is not functioning.

Please contact Microsoft Product Support Services for further help.

Additional information: Unknown media status code.

C:\Documents and Settings\Fretshop>

And from the third:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Toolboy>nbtstat -n

Wireless Network Connection:
Node IpAddress: [192.168.0.102] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
FRETSHOPINTAKE <00> UNIQUE Registered
FRETSHOPINTAKE <20> UNIQUE Registered
TOAD <00> GROUP Registered
TOAD <1E> GROUP Registered

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

C:\Documents and Settings\Toolboy>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : FretshopIntake
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Adapte
r II
Physical Address. . . . . . . . . : 00-0E-9B-59-23-D1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, November 23, 2007 10:52:07 A
M
Lease Expires . . . . . . . . . . : Friday, November 30, 2007 10:52:07 A
M

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile Connecti
on
Physical Address. . . . . . . . . : 00-11-25-30-F1-EE

C:\Documents and Settings\Toolboy>

johnwill · 11-23-2007, 02:29 PM

That all looks fine. Here's a set of procedures to walk through to find out why you're failing to network.

Turn off any firewalls for debugging. If the firewall is the problem, you'll have to configure it to allow access to "trusted zone" addresses. Note that some firewalls must be completely uninstalled to stop them from affecting your networking.

Start, Run, CMD to open a command prompt for the following commands.

PING each remote computer by IP address, and if successful, PING by name. Open a command prompt as described above and type.

PING <ip address>
or
PING <computer name>

Where:
<ip address> - is the x.x.x.x IP address
<computer name> - is the computer name

A failure to PING is almost always a firewall configuration issue. Any failure to PING needs to be corrected before you go any farther.

Note: You can obtain the IP address and computer name of a computer by opening a command prompt (DOS window) and typing IPCONFIG /ALL. This should work for any Windows version. The IPCONFIG /ALL display will provide a wealth of useful information for debugging your network connection.

Check your Services are Started on all PCs:

Computer Browser
DHCP Client
DNS Client
Network Connections
Network Location Awareness
Remote Procedure Call (RPC)
Server
TCP/IP Netbios helper
Workstation

Note: You can check the services in Control Panel, Administrative Tools, Services.

All of these services should be started, and their startup type should be automatic.

All computers should be in the same workgroup for computer browsing to function properly. File & Print Sharing has to be enabled on any computer you wish to share files or printers from. You also need to actually share the resource in question from My Computer, right click on the drive/printer/folder, and select sharing.

If you encounter difficulties accessing computers that are visible in Network Neighborhood, make sure the computer being accessed has an account with the same name/password as the system connecting to it uses to login.

While the default NetBIOS setting is correct for normal network configurations, it's possible for it to be altered, and it costs nothing to make sure it's correct. NETBIOS over TCP/IP must be enabled for normal network browsing.

Uncletoad · 11-23-2007, 02:54 PM

Thanks for taking time to assist me with this. I appreciate the consideration.

This was on two of the machines when I tried the ipconfig /all comand

Quote:

Originally Posted by Uncletoad

C:\Documents and Settings\Fretshop>ipconfig /all

Windows IP Configuration

An internal error occurred: A device attached to the system is not functioning.

Please contact Microsoft Product Support Services for further help.

Additional information: Unknown media status code.

C:\Documents and Settings\Fretshop>

Is that wierd?

I've looked at the other things you've mentioned and they are all as prescribed except I'm not sure what you mean here

Quote:

Originally Posted by johnwill

While the default NetBIOS setting is correct for normal network configurations, it's possible for it to be altered, and it costs nothing to make sure it's correct. NETBIOS over TCP/IP must be enabled for normal network browsing.

What's next?

johnwill · 11-24-2007, 06:56 AM

Well, that result with IPCONFIG is bad!

On those machines, please do this.

TCP/IP stack repair options for use with Windows XP with SP2.

Start, Run, CMD to open a command prompt:

Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log

Reset WINSOCK entries to installation defaults: netsh winsock reset catalog

Reboot the machine.

Uncletoad · 11-24-2007, 07:14 AM

Ah. Thought so.

Monday. I can't bear to go in on weekends.

johnwill · 11-24-2007, 07:17 AM

Let us know.

Uncletoad · 11-24-2007, 12:12 PM

I just did this on the one that travels...the T42p I'm using now at home.

Same result after the reset process.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Phil Maneri>ipconfig /all

Windows IP Configuration

An internal error occurred: A device attached to the system is not functioning.

Please contact Microsoft Product Support Services for further help.

Additional information: Unknown media status code.

C:\Documents and Settings\Phil Maneri>

johnwill · 11-25-2007, 07:37 AM

See if this page addresses that error: http://forums.speedguide.net/showthread.php?t=217829

Uncletoad · 11-26-2007, 07:40 AM

Quote:

Originally Posted by johnwill

See if this page addresses that error: http://forums.speedguide.net/showthread.php?t=217829

That's really interesting. The one machine that did a proper ipconfig was the one with an older driver. Dunno why that one has an older driver. I rolled back the drivers on the other two so they all have the same early driver and ipconfig works just fine.

Here are the results, everything still won't talk to each other...

From the T42p:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Phil Maneri>nbtstat -n

Wireless Network Connection:
Node IpAddress: [192.168.0.112] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
UNCLETOAD <00> UNIQUE Registered
UNCLETOAD <20> UNIQUE Registered
TOAD <00> GROUP Registered
TOAD <1E> GROUP Registered
TOAD <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Bluetooth Network Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

C:\Documents and Settings\Phil Maneri>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : UNCLETOAD
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Adapte
r
Physical Address. . . . . . . . . : 00-05-4E-51-14-54
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Monday, November 26, 2007 10:19:40 A
M
Lease Expires . . . . . . . . . . : Monday, December 03, 2007 10:19:40 A
M

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile Connecti
on
Physical Address. . . . . . . . . : 00-15-58-09-2B-DA

Ethernet adapter Bluetooth Network Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Netw
ork)
Physical Address. . . . . . . . . : 00-0F-B3-9D-5A-1A

C:\Documents and Settings\Phil Maneri>

From another T42:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Fretshop>nbtstat -n

Wireless Network Connection 2:
Node IpAddress: [192.168.0.111] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
FRETSHOPMAIN <00> UNIQUE Registered
FRETSHOPMAIN <20> UNIQUE Registered
TOAD <00> GROUP Registered
TOAD <1E> GROUP Registered

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

C:\Documents and Settings\Fretshop>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : FretshopMain
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Adapte
r II
Physical Address. . . . . . . . . : 00-0E-9B-59-20-B8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.111
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Monday, November 26, 2007 10:21:54 A
M
Lease Expires . . . . . . . . . . : Monday, December 03, 2007 10:21:54 A
M

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile Connecti
on
Physical Address. . . . . . . . . : 00-11-25-46-01-1F

C:\Documents and Settings\Fretshop>

and from the third T42:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Toolboy>nbtstat -n

Wireless Network Connection:
Node IpAddress: [192.168.0.102] Scope Id: []

NetBIOS Local Name Table

Name Type Status
---------------------------------------------
FRETSHOPINTAKE <00> UNIQUE Registered
FRETSHOPINTAKE <20> UNIQUE Registered
TOAD <00> GROUP Registered
TOAD <1E> GROUP Registered
TOAD <1D> UNIQUE Registered
..__MSBROWSE__.<01> GROUP Registered

Local Area Connection:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

C:\Documents and Settings\Toolboy>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : FretshopIntake
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Adapte
r II
Physical Address. . . . . . . . . : 00-0E-9B-59-23-D1
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Monday, November 26, 2007 10:02:34 A
M
Lease Expires . . . . . . . . . . : Monday, December 03, 2007 10:02:34 A
M

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile Connecti
on
Physical Address. . . . . . . . . : 00-11-25-30-F1-EE

C:\Documents and Settings\Toolboy>

What's next?

Uncletoad · 11-26-2007, 08:41 AM

Just for kicks I hardwired all three through the network router. After rebooting and looking for each computer through windows network they all three see each other that way. The only glitch is that the T42p requires a password to see it from the other two. coincidentally it's the only computer I've put a password on all the user accounts.

That in and of itself isn't a problem.

Issue of course is that I need two of those boxes to be wireless. The main one "Fretshopmain" stays in a docking station with another monitor attached to it. It could remain wired. The T42p is mobile, the other is ranging away from a LAN cable.

fwiw changing to all the same older LAN driver fixed that wired networking weirdness.

11-21-2007, 07:03 PM	#1 (permalink)
Uncletoad Registered User Join Date: Oct 2007 Location: The Land of Cows Posts: 32 OS: Windows XP Pro SP2 My System	Can't get three computers on wireless network to work with each other. I have two identical IBM T42 notebooks on a network at my business, one lives in a dock still using wireless connections for LAN. I have an IBM T42p that travels back and forth between there and home where another T42 lives. I have Dlink 624 routers at both places. The workgroup name is the same both places. I can ping all the boxes at any place all the time. Frequently (more often than not) the computers don't see each other. Can someone point me to a process to troubleshoot this? I'm attempting to run Quickbooks multiuser mode through the Network and can't get it to work if the boxes don't reliably see each other. I'm using Windows to configure my wireless connections not IBM's Access Connections. All three computers at work have fresh images within the last month. I gave up on my recent image with the T42p and have just finished redoing it again. Still have the same problems. Windows XP Pro on all computers. None have ever had problems getting on the internet through the network.

11-22-2007, 07:31 AM	#2 (permalink)
BMR777 Tech, Microsoft Support Join Date: Apr 2005 Location: Chicago, IL Posts: 1,392 OS: XP Pro, XP Home, Vista Home Basic, Ubuntu Studio Blog Entries: 2	Re: Can't get three computers on wireless network to work with each other. When you imaged them, did you give them the same image? There might be a slight chance that all of the computers have the same computer name due to the imaging, which can cause confilcts. Right click on My Computer, select properties and then go to the Computer Name tab. Check that the name is different on all of the PCs. Also make sure no other PCs on the network have the same name. If it is the same, change the computer name to something unique on all computers. BMR777 __________________ Brandon Rusnak Protection: AVG Free Anti Virus :: Windows Defender :: Hosts File :: SiteAdvisor :: ZoneAlarm Quick Fixes: 5 Steps to remove spyware

11-22-2007, 07:57 AM	#3 (permalink)
Uncletoad Registered User Join Date: Oct 2007 Location: The Land of Cows Posts: 32 OS: Windows XP Pro SP2 My System	Re: Can't get three computers on wireless network to work with each other. Names are all different. Usernames are all different. I used the original image format CD's and added the software and files we use but each box is an individual.

11-22-2007, 09:55 AM	#4 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 29,829 OS: XP-Pro, Vista, Linux Blog Entries: 1	Re: Can't get three computers on wireless network to work with each other. Let's see this for each computer when they're all connected to the network. Start, Run, CMD to open a command prompt: Type the following two commands: nbtstat -n ipconfig /all Right click in the command window and choose Select All, then hit Enter. Paste the results in a message here. If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

11-23-2007, 07:58 AM	#5 (permalink)
Uncletoad Registered User Join Date: Oct 2007 Location: The Land of Cows Posts: 32 OS: Windows XP Pro SP2 My System	Re: Can't get three computers on wireless network to work with each other. From the T42p: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Phil Maneri>nbtstat-n 'nbtstat-n' is not recognized as an internal or external command, operable program or batch file. C:\Documents and Settings\Phil Maneri>nbtstat -n Wireless Network Connection: Node IpAddress: [192.168.0.112] Scope Id: [] NetBIOS Local Name Table Name Type Status --------------------------------------------- UNCLETOAD <00> UNIQUE Registered UNCLETOAD <20> UNIQUE Registered TOAD <00> GROUP Registered TOAD <1E> GROUP Registered Local Area Connection: Node IpAddress: [0.0.0.0] Scope Id: [] No names in cache Bluetooth Network Connection: Node IpAddress: [0.0.0.0] Scope Id: [] No names in cache C:\Documents and Settings\Phil Maneri>ipconfig /all Windows IP Configuration An internal error occurred: A device attached to the system is not functioning. Please contact Microsoft Product Support Services for further help. Additional information: Unknown media status code. C:\Documents and Settings\Phil Maneri> And from the second T42: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Fretshop>ntbstat -n 'ntbstat' is not recognized as an internal or external command, operable program or batch file. C:\Documents and Settings\Fretshop>nbtstat -n Wireless Network Connection 2: Node IpAddress: [192.168.0.111] Scope Id: [] NetBIOS Local Name Table Name Type Status --------------------------------------------- FRETSHOPMAIN <00> UNIQUE Registered FRETSHOPMAIN <20> UNIQUE Registered TOAD <00> GROUP Registered TOAD <1E> GROUP Registered TOAD <1D> UNIQUE Registered ..__MSBROWSE__.<01> GROUP Registered Local Area Connection: Node IpAddress: [0.0.0.0] Scope Id: [] No names in cache C:\Documents and Settings\Fretshop>ipconfig /all Windows IP Configuration An internal error occurred: A device attached to the system is not functioning. Please contact Microsoft Product Support Services for further help. Additional information: Unknown media status code. C:\Documents and Settings\Fretshop> And from the third: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Toolboy>nbtstat -n Wireless Network Connection: Node IpAddress: [192.168.0.102] Scope Id: [] NetBIOS Local Name Table Name Type Status --------------------------------------------- FRETSHOPINTAKE <00> UNIQUE Registered FRETSHOPINTAKE <20> UNIQUE Registered TOAD <00> GROUP Registered TOAD <1E> GROUP Registered Local Area Connection: Node IpAddress: [0.0.0.0] Scope Id: [] No names in cache C:\Documents and Settings\Toolboy>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : FretshopIntake Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : 11a/b/g Wireless LAN Mini PCI Adapte r II Physical Address. . . . . . . . . : 00-0E-9B-59-23-D1 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.0.102 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 Lease Obtained. . . . . . . . . . : Friday, November 23, 2007 10:52:07 A M Lease Expires . . . . . . . . . . : Friday, November 30, 2007 10:52:07 A M Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile Connecti on Physical Address. . . . . . . . . : 00-11-25-30-F1-EE C:\Documents and Settings\Toolboy>

11-23-2007, 02:29 PM	#6 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 29,829 OS: XP-Pro, Vista, Linux Blog Entries: 1	Re: Can't get three computers on wireless network to work with each other. That all looks fine. Here's a set of procedures to walk through to find out why you're failing to network. Turn off any firewalls for debugging. If the firewall is the problem, you'll have to configure it to allow access to "trusted zone" addresses. Note that some firewalls must be completely uninstalled to stop them from affecting your networking. Start, Run, CMD to open a command prompt for the following commands. PING each remote computer by IP address, and if successful, PING by name. Open a command prompt as described above and type. PING <ip address> or PING <computer name> Where: <ip address> - is the x.x.x.x IP address <computer name> - is the computer name A failure to PING is almost always a firewall configuration issue. Any failure to PING needs to be corrected before you go any farther. Note: You can obtain the IP address and computer name of a computer by opening a command prompt (DOS window) and typing IPCONFIG /ALL. This should work for any Windows version. The IPCONFIG /ALL display will provide a wealth of useful information for debugging your network connection. Check your Services are Started on all PCs: Computer Browser DHCP Client DNS Client Network Connections Network Location Awareness Remote Procedure Call (RPC) Server TCP/IP Netbios helper Workstation Note: You can check the services in Control Panel, Administrative Tools, Services. All of these services should be started, and their startup type should be automatic. All computers should be in the same workgroup for computer browsing to function properly. File & Print Sharing has to be enabled on any computer you wish to share files or printers from. You also need to actually share the resource in question from My Computer, right click on the drive/printer/folder, and select sharing. If you encounter difficulties accessing computers that are visible in Network Neighborhood, make sure the computer being accessed has an account with the same name/password as the system connecting to it uses to login. While the default NetBIOS setting is correct for normal network configurations, it's possible for it to be altered, and it costs nothing to make sure it's correct. NETBIOS over TCP/IP must be enabled for normal network browsing. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

11-24-2007, 06:56 AM	#8 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 29,829 OS: XP-Pro, Vista, Linux Blog Entries: 1	Re: Can't get three computers on wireless network to work with each other. Well, that result with IPCONFIG is bad! On those machines, please do this. TCP/IP stack repair options for use with Windows XP with SP2. Start, Run, CMD to open a command prompt: Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log Reset WINSOCK entries to installation defaults: netsh winsock reset catalog Reboot the machine. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

11-24-2007, 07:14 AM	#9 (permalink)
Uncletoad Registered User Join Date: Oct 2007 Location: The Land of Cows Posts: 32 OS: Windows XP Pro SP2 My System	Re: Can't get three computers on wireless network to work with each other. Ah. Thought so. Monday. I can't bear to go in on weekends.

11-24-2007, 07:17 AM	#10 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 29,829 OS: XP-Pro, Vista, Linux Blog Entries: 1	Re: Can't get three computers on wireless network to work with each other. Let us know. __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

11-24-2007, 12:12 PM	#11 (permalink)
Uncletoad Registered User Join Date: Oct 2007 Location: The Land of Cows Posts: 32 OS: Windows XP Pro SP2 My System	Re: Can't get three computers on wireless network to work with each other. I just did this on the one that travels...the T42p I'm using now at home. Same result after the reset process. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Phil Maneri>ipconfig /all Windows IP Configuration An internal error occurred: A device attached to the system is not functioning. Please contact Microsoft Product Support Services for further help. Additional information: Unknown media status code. C:\Documents and Settings\Phil Maneri>

11-25-2007, 07:37 AM	#12 (permalink)
johnwill Manager, Networking Forums Join Date: Sep 2002 Location: S.E. Pennsylvania, US Posts: 29,829 OS: XP-Pro, Vista, Linux Blog Entries: 1	Re: Can't get three computers on wireless network to work with each other. See if this page addresses that error: http://forums.speedguide.net/showthread.php?t=217829 __________________ If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience

11-26-2007, 08:41 AM	#14 (permalink)
Uncletoad Registered User Join Date: Oct 2007 Location: The Land of Cows Posts: 32 OS: Windows XP Pro SP2 My System	Re: Can't get three computers on wireless network to work with each other. Just for kicks I hardwired all three through the network router. After rebooting and looking for each computer through windows network they all three see each other that way. The only glitch is that the T42p requires a password to see it from the other two. coincidentally it's the only computer I've put a password on all the user accounts. That in and of itself isn't a problem. Issue of course is that I need two of those boxes to be wireless. The main one "Fretshopmain" stays in a docking station with another monitor attached to it. It could remain wired. The T42p is mobile, the other is ranging away from a LAN cable. fwiw changing to all the same older LAN driver fixed that wired networking weirdness.