Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Network Connection Fail


  • Please log in to reply
7 replies to this topic

#1 Kevinbbb

Kevinbbb

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:01:07 PM

Posted 19 April 2007 - 10:16 PM

My goal is to Network 2 laptops both using XP Home with servicepacks etc.
Could not see any workgroups - Used Diagnostics that said the Network Adaptor FAILED.
I confirmed this trying manual pinging.
Both laptops work reliably connecting to my ISP seperately and when using the Linksys WRT54GS in front of them.
Acer 3690 Network diagnostics all PASS
Presario 2800 Network diagnostics FAIL for adaptor.
I can ping the Acer OK from the Presario but not he Presario from the acer.
I can ping the Router or my ISP etc from both laptops.
Tried uninstalling the Presario adaptor driver, finding better or later driver to no avail.
Device manager says it is working OK.
I have searched online for days for help and this groups postings but have turned up nothing to fix things.
Learned a lot abt TCP/IP but no solution. The Microsoft Networking Trouble shooting article was informative.
This is my first post to this group and welcome any help.
Tnx Kevin in Phoenix Az

BC AdBot (Login to Remove)

 


#2 nigglesnush85

nigglesnush85

  • Members
  • 4,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:UK
  • Local time:08:07 PM

Posted 20 April 2007 - 07:10 AM

Hello and welcome,

Could you tell what firewalls the two separate firewalls are using? also have you tried assigning the two systems their own IP address? open control panel and select network connections right click the connection that you are using, select properties and scroll down the list that is displayed. select internet protocol TCP/IP and click properties. are both the systems on the same subnet?
Regards,

Alan.

#3 Erik the Expert

Erik the Expert

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:01:07 PM

Posted 20 April 2007 - 11:31 AM

Sounds completely like a firewall issue on the computer that is not replying to the ping. On the older firewalls like 1 year ago or more you have to go into the options. ALL OF THEM ARE DIFFERENT and under network you need to allow your subnet. Normally 192.168.0.1-192.168.0.255 or 192.168.1.1-192.168.1.255 this can be determined by clicking start --> Run --> cmd --> BLACK SCREEN --> ipconfig --> then look @ your IP Address and use the 3rd octet 192.168.(THIS #).??? for your allowed traffic.

You might have to do this on both computers but it sounds like just one is giving you trouble. Also you need to have passwords on your computers in order for windows XP networking to work properly. Hope this helps!

#4 Kevinbbb

Kevinbbb
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:01:07 PM

Posted 20 April 2007 - 04:32 PM

I should have said in my original post that I had Windows firewall TURNED OFF on both laptops and ALL virus checking etc was OFF - at least everything I am aware of. Until I can get the older Presario to PASS on Diagnostics / responding to PING - no hope of networking yet.
Not very confident in what I'm doing but I did try MANUAL setting for the Intel Network adaptor, did not put in a default gateway value and the Diagnostic failed to ping my ISP also. I assume if I set manually the (DHCP?) does not auto assign?? Put it back to auto - rebooted and working ok with ISP and still fails on the Network adaptor. Frustrating few days but a good learning experience. Tnx guys.

#5 nigglesnush85

nigglesnush85

  • Members
  • 4,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:UK
  • Local time:08:07 PM

Posted 20 April 2007 - 05:30 PM

If you set up the connection manually, the DHCP will not automatically configure for you. are both the systems using the same subnet mask?
Regards,

Alan.

#6 Kevinbbb

Kevinbbb
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:01:07 PM

Posted 21 April 2007 - 01:16 PM

As far as I can see the Subnet mask is always 255.255.255.0
ipconfig shows same settings in both laptops except the last octet for IP Address,
Presario = 101 and Acer = 100.
But is this relevant if the Presario is still failing diagnostics when used totally seperate form the router and other computer.

From a cold boot with just the motorola SB5120 and Presario it fails - complete listing below.
If I had never started on networking the 2 laptops I would never have been aware of any problem.
Presario works fine for email and the Internet and still does.
In this setup ie just Presario and Motorola SB120
ipcongfig gives Subnet Mask 255.255.248.0
IP address 68.106.35.59 and fails when I ping it.

Both computers access the net with the SB5120/router.
Presario hardwired - Acer wireless to router.

Seperate question:getting ahead of myself!
When doing Windows networking how many networks can on setup?
And how does one check to see what networks have been created?
Should "View workgroup computers" show this.
I always get none available and the no permission message - obviously I am Administrator
Tnx agn Kevin (ready to give up altho' I'm sure theres a simple solution)

Network Diagnostics FOR Presario 4 21 2007
Cox cable to Motorola SB5120 to Presario -NO router NO second Laptop

Scan your system
Set scanning options
99%
Formatting Results
Options

Actions
Ping
Connect
Show
Verbose
Save to Desktop

Categories
Mail Service
News Service
Internet Proxy Server
Computer Information
Operating System
Windows Version
Modems
Network Clients
Network Adapters
Domain Name System (DNS)
Dynamic Host Configuration Protocol (DHCP)
Default Gateways
Internet Protocol Address
Windows Internet Naming Service (WINS)

Show Saved Files
Internet Service
Default Outlook Express Mail pop.west.cox.net / smtp.west.cox.net PASSED
InBoundMailPort = 110
InBoundMailServer = pop.west.cox.net (PASSED)
Pinging pop.west.cox.net [68.6.19.2] with 32 bytes of data:
Reply from 68.6.19.2: bytes=32 time=16ms TTL=16
Reply from 68.6.19.2: bytes=32 time=20ms TTL=20
Reply from 68.6.19.2: bytes=32 time=17ms TTL=17
Reply from 68.6.19.2: bytes=32 time=18ms TTL=18
Ping statistics for 68.6.19.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 20ms, Average = 17ms
InBoundMailType = POP3
Successfully connected to pop.west.cox.net port 110
OutBoundMailPort = 25
OutBoundMailServer = smtp.west.cox.net (PASSED)
Pinging smtp.west.cox.net [68.6.19.4] with 32 bytes of data:
Reply from 68.6.19.4: bytes=32 time=18ms TTL=18
Reply from 68.6.19.4: bytes=32 time=18ms TTL=18
Reply from 68.6.19.4: bytes=32 time=692ms TTL=692
Reply from 68.6.19.4: bytes=32 time=18ms TTL=18
Ping statistics for 68.6.19.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 692ms, Average = 186ms
OutBoundMailType = SMTP
Successfully connected to smtp.west.cox.net port 25
Default Outlook Express News Not Configured
Internet Explorer Web Proxy Not Configured
Computer Information
Computer System FORMAT11252006
AdminPasswordStatus = 0
AutomaticResetBootOption = TRUE
AutomaticResetCapability = TRUE
BootROMSupported = TRUE
BootupState = Normal boot
Caption = FORMAT11252006
ChassisBootupState = 3
CreationClassName = Win32_ComputerSystem
CurrentTimeZone = -420
Description = AT/AT COMPATIBLE
Domain = HOME
DomainRole = 0
EnableDaylightSavingsTime = FALSE
FrontPanelResetStatus = 2
InfraredSupported = TRUE
KeyboardPasswordStatus = 0
Manufacturer = Compaq
Model = Presario 2800
Name = FORMAT11252006
NetworkServerModeEnabled = TRUE
NumberOfProcessors = 1
OEMStringArray = www.compaq.com
PartOfDomain = FALSE
PauseAfterReset = -1
PowerOnPasswordStatus = 0
PowerState = 0
PowerSupplyState = 3
PrimaryOwnerName = Kevin Bierney
ResetCapability = 1
ResetCount = -1
ResetLimit = -1
Roles
LM_Workstation
LM_Server
Print
NT
Potential_Browser
Master_Browser
Status = OK

SystemStartupDelay = 30
SystemStartupOptions = "Microsoft Windows XP Home Edition" /fastdetect /NoExecute=OptIn
SystemStartupSetting = 0
SystemType = X86-based PC
ThermalState = 3
TotalPhysicalMemory = 536199168
UserName = FORMAT11252006\Kevin Bierney
WakeUpType = 6
Operating System Microsoft Windows XP Home Edition
BootDevice = \Device\HarddiskVolume1
BuildNumber = 2600
BuildType = Uniprocessor Free
Caption = Microsoft Windows XP Home Edition
CodeSet = 1252
CountryCode = 1
CreationClassName = Win32_OperatingSystem
CSCreationClassName = Win32_ComputerSystem
CSDVersion = Service Pack 2
CSName = FORMAT11252006
CurrentTimeZone = -420
DataExecutionPrevention_32BitApplications = FALSE
DataExecutionPrevention_Available = FALSE
DataExecutionPrevention_Drivers = FALSE
DataExecutionPrevention_SupportPolicy = 2
Debug = FALSE
Description = KEVIN
Distributed = FALSE
EncryptionLevel = 168
ForegroundApplicationBoost = 2
FreePhysicalMemory = 285292
FreeSpaceInPagingFiles = 1062912
FreeVirtualMemory = 2053504
InstallDate = 4:33:41 PM 11/25/2006
LargeSystemCache = 0
LastBootUpTime = 8:20:13 AM 4/21/2007
LocalDateTime = 8:23:01 AM 4/21/2007
Locale = 0409
Manufacturer = Microsoft Corporation
MaxNumberOfProcesses = -1
MaxProcessMemorySize = 2097024
Name = Microsoft Windows XP Home Edition|C:\WINDOWS|\Device\Harddisk0\Partition1
NumberOfProcesses = 45
NumberOfUsers = 2
OSLanguage = 1033
OSType = 18
Primary = TRUE
ProductType = 1
QuantumLength = 0
QuantumType = 0
RegisteredUser = Kevin Bierney
SerialNumber
ServicePackMajorVersion = 2
ServicePackMinorVersion = 0
SizeStoredInPagingFiles = 1277872
Status = OK
SuiteMask = 784
SystemDevice = \Device\HarddiskVolume1
SystemDirectory = C:\WINDOWS\system32
SystemDrive = C:
TotalVirtualMemorySize = 2097024
TotalVisibleMemorySize = 523632
Version = 5.1.2600
WindowsDirectory = C:\WINDOWS
Version 5.1.2600
Version = 5.1.2600
BuildVersion = 2600.0000
Modems and Network Adapters
Modems
Lucent Win Modem
AttachedTo = COM4
BlindOff = X4
BlindOn = X3
Caption = Lucent Win Modem
CompressionOff = %C0
CompressionOn = %C1
ConfigurationDialog = modemui.dll
CountrySelected = United States
CreationClassName = Win32_PotsModem
DCB
28
0
0
0
0
194
1
0
21
32
0
0
0
0
Default
60
0
0
0
0
0
0
0
0
0
Description = Lucent Win Modem
DeviceID = Modem0
DeviceType = Internal Modem
DriverDate = 5:00:00 PM 3/8/2000
ErrorControlForced = \N4
ErrorControlOff = \N1
ErrorControlOn = \N3
FlowControlHard = &K3
FlowControlOff = &K0
FlowControlSoft = &K4
InactivityScale = "3c000000"
InactivityTimeout = 0
Index = 0
MaxBaudRateToSerialPort = 115200
Model = Lucent Win Modem
ModemInfPath = mdmlt3.inf
ModemInfSection = Modem_PNP_DF
ModulationBell = B1B16B2
ModulationCCITT = B0B15B2
Name = Lucent Win Modem
PortSubClass = "02"
PowerManagementSupported = FALSE
Prefix = AT
Properties
192
1
0
0
255
0
0
0
255
0
0
0
7
0
0
0
ProviderName = Microsoft
Pulse = P
Reset = AT&F
ResponsesKeyName = Lucent Win Modem::Lucent::Microsoft
SpeakerModeDial = M1
SpeakerModeOff = M0
SpeakerModeOn = M2
SpeakerModeSetup = M3
SpeakerVolumeHigh = L3
SpeakerVolumeLow = L0
SpeakerVolumeMed = L2
Status = Unknown
StatusInfo = 2
SystemCreationClassName = Win32_ComputerSystem
SystemName = FORMAT11252006
Terminator =
Tone = T
Conexant HSFi V.9x MiniPCI Modem
AttachedTo = COM5
BlindOff = X4
BlindOn = X3
Caption = Conexant HSFi V.9x MiniPCI Modem
CompressionOff = +DS=0;
CompressionOn = +DS=3;
ConfigManagerErrorCode = 0
ConfigManagerUserConfig = FALSE
ConfigurationDialog = modemui.dll
CountrySelected = United States
CreationClassName = Win32_PotsModem
DCB
28
0
0
0
0
194
1
0
21
32
0
0
0
0
Default
60
0
0
0
0
0
0
0
0
0
Description = Conexant HSFi V.9x MiniPCI Modem
DeviceID = PCI\VEN_14F1&DEV_2F00&SUBSYS_8D880E11&REV_01\4&139E449D&0&20F0
DeviceType = Internal Modem
DriverDate = 5:00:00 PM 9/10/2003
ErrorControlForced = +ES=3,2,4;
ErrorControlOff = +ES=1,0,1;
ErrorControlOn = +ES=3,0,2;
FlowControlHard = +IFC=2,2;
FlowControlOff = +IFC=0,0;
FlowControlSoft = +IFC=1,1;
Index = 1
MaxBaudRateToSerialPort = 115200
Model = Conexant HSFi V.9x MiniPCI Modem
ModemInfPath = oem1.inf
ModemInfSection = ModemX
Name = Conexant HSFi V.9x MiniPCI Modem
PNPDeviceID = PCI\VEN_14F1&DEV_2F00&SUBSYS_8D880E11&REV_01\4&139E449D&0&20F0
PortSubClass = "02"
PowerManagementSupported = FALSE
Prefix = AT
Properties
192
1
0
0
255
0
0
0
0
0
0
0
0
0
0
0
ProviderName = Conexant
Pulse = P
Reset = ATZ
ResponsesKeyName = Conexant HSFi V.9x MiniPCI Modem::Conexant::Conexant
SpeakerModeDial = M1
SpeakerModeOff = M0
SpeakerModeOn = M2
SpeakerModeSetup = M3
SpeakerVolumeHigh = L3
SpeakerVolumeLow = L1
SpeakerVolumeMed = L2
Status = OK
StatusInfo = 3
SystemCreationClassName = Win32_ComputerSystem
SystemName = FORMAT11252006
Terminator =
Tone = T
Network Adapters [00000001] Intel® PRO/100 VE Network Connection FAILED
Caption = [00000001] Intel® PRO/100 VE Network Connection
DatabasePath = %SystemRoot%\System32\drivers\etc
DefaultIPGateway = 68.106.32.1(Same Subnet) (PASSED)
Pinging 68.106.32.1 with 32 bytes of data:
Reply from 68.106.32.1: bytes=32 time=7ms TTL=7
Reply from 68.106.32.1: bytes=32 time=7ms TTL=7
Reply from 68.106.32.1: bytes=32 time=6ms TTL=6
Reply from 68.106.32.1: bytes=32 time=8ms TTL=8
Ping statistics for 68.106.32.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 8ms, Average = 7ms
Description = Intel® PRO/100 VE Network Connection - Packet Scheduler Miniport
DHCPEnabled = TRUE
DHCPLeaseExpires = 8:20:50 AM 4/22/2007
DHCPLeaseObtained = 8:20:50 AM 4/21/2007
DHCPServer = 172.19.73.31 (PASSED)
Pinging 172.19.73.31 with 32 bytes of data:
Reply from 172.19.73.31: bytes=32 time=9ms TTL=9
Reply from 172.19.73.31: bytes=32 time=7ms TTL=7
Reply from 172.19.73.31: bytes=32 time=7ms TTL=7
Reply from 172.19.73.31: bytes=32 time=7ms TTL=7
Ping statistics for 172.19.73.31:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 9ms, Average = 7ms
DNSDomain = ph.cox.net
DNSEnabledForWINSResolution = FALSE
DNSHostName = Format11252006
DNSServerSearchOrder (PASSED)
68.2.16.25 (PASSED)
Pinging 68.2.16.25 with 32 bytes of data:
Reply from 68.2.16.25: bytes=32 time=7ms TTL=7
Reply from 68.2.16.25: bytes=32 time=8ms TTL=8
Reply from 68.2.16.25: bytes=32 time=8ms TTL=8
Reply from 68.2.16.25: bytes=32 time=7ms TTL=7
Ping statistics for 68.2.16.25:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms
68.2.16.30 (PASSED)
Pinging 68.2.16.30 with 32 bytes of data:
Reply from 68.2.16.30: bytes=32 time=8ms TTL=8
Reply from 68.2.16.30: bytes=32 time=7ms TTL=7
Reply from 68.2.16.30: bytes=32 time=7ms TTL=7
Reply from 68.2.16.30: bytes=32 time=8ms TTL=8
Ping statistics for 68.2.16.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 8ms, Average = 7ms
68.6.16.30 (PASSED)
Pinging 68.6.16.30 with 32 bytes of data:
Reply from 68.6.16.30: bytes=32 time=17ms TTL=17
Reply from 68.6.16.30: bytes=32 time=14ms TTL=14
Reply from 68.6.16.30: bytes=32 time=16ms TTL=16
Reply from 68.6.16.30: bytes=32 time=17ms TTL=17
Ping statistics for 68.6.16.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 17ms, Average = 16ms
DomainDNSRegistrationEnabled = FALSE
FullDNSRegistrationEnabled = TRUE
GatewayCostMetric = 20
Index = 1
IPAddress = 68.106.35.59 (FAILED)
Pinging 68.106.35.59 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 68.106.35.59:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
IPConnectionMetric = 20
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.248.0
IPXEnabled = FALSE
MACAddress = 00:08:02:66:18:93
ServiceName = E100B
SettingID = {EA777C85-AB57-4A0B-B7B1-D836A98B85D6}
TcpipNetbiosOptions = 1
TcpMaxDataRetransmissions = 7
WINSEnableLMHostsLookup = TRUE
Network Clients
Microsoft Terminal Services
Description = RDPNP
Manufacturer = Microsoft Corporation
Name = Microsoft Terminal Services
Status = Unknown
Microsoft Windows Network
Caption = Workstation
Description = Creates and maintains client network connections to remote servers. If this service is stopped, these connections will be unavailable. If this service is disabled, any services that explicitly depend on it will fail to start.
Manufacturer = Microsoft Corporation
Name = Microsoft Windows Network
Status = OK
Web Client Network
Caption = WebClient
Description = Enables Windows-based programs to create, access, and modify Internet-based files. If this service is stopped, these functions will not be available. If this service is disabled, any services that explicitly depend on it will fail to start.
Manufacturer = Microsoft Corporation
Name = Web Client Network
Status = OK

#7 Kevinbbb

Kevinbbb
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:01:07 PM

Posted 21 April 2007 - 08:39 PM

I just spent some time with a neighbor having the same apparent networking problem.
Her desktop FAILS the Diagnostic test. Her wireless laptop PASSES. Both her computers are totally different models from mine. Both work ok on the net but can't network for file or printer sharing. Only commonality we have is Cox Cable, XP Home and the same Linksys wireless router.

#8 nigglesnush85

nigglesnush85

  • Members
  • 4,371 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:UK
  • Local time:08:07 PM

Posted 22 April 2007 - 07:07 AM

you mentioned that the last octet of the two systems were 100 and 101. Try changing them to 104 and 105, it could be that the router is using 100 or 101, this happened on a similar set up here, changing the last octet of the IP solved the problem. if both of the systems are on the same subnet, they should be communicating with each other, have you put both the systems on the same workgroup? there is a handy network tool that should help you with setting up networks http://www.networkmagic.com/
Regards,

Alan.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users