Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot ping router or other machine but can get on internet 2

Status
Not open for further replies.

brettban

Technical User
Aug 7, 2002
14
My set-up is as follows - Router -- Linksys BEFSR41, two machines (laptops w/ Windows XP Home). Using router's DHCP so IPs are as follows - 192.168.1.1 router - machines A & B are 192.168.1.2 & 3 respectively. Internet connection is SWBell DSL. I can get on the internet with no problems on both machines; however machine B cannot ping the router or access it through the browser. And neither computer can see each other on the network. Machine A can ping the router and itself but not Machine B. Any suggestions on what's wrong with Machine B?
 
First Q (not that it really matters) - did you change the default DHCP range? The defaut DHCP starting address is 192.168.1.100

Second Q - are there firewalls running on the pc's? This includes XP's built-in, Zone Alarm, McAfee's, Norton's.

Third Q - is the workgroup name the same on both pc's?
 
Q1 - I did change the default IP ranges. Set-up as three user w/ starting IP 192.168.1.2
Q2 - I disabled the Windows XP firewall on both computers
Q3 - Both computers have the same Workgroup name.

Since my first post - I added the NetBIOS protocol on both computers and now both show up on the network. However, I didn't think Windows XP used or even need that protocol. Also, Machine B still cannot ping or web access the router.
 
Do you have any VPN software installed on system??
I had exact same problem - not being able to ping or access router with wireless cards (linksy wmp11 in desktop and linksys 54g wireless notebook). Router is Linksys WRT54G.
Internet access was great!!! Just no local lan.
I disabled VPN software in MSCONFIG--->Startup.
Now have full access to each machine from each other, each machine can ping each other, each machine can now ping router and access webadmin page. Net access still works.
Al
 
brettban,

Netbios is the core of Microsoft Networking for client naming. It is not an incidental part, it is a core naming service.

For problem box B, do an IPCONFIG /all and see if it obtained the IP address 192.168.1.x, that the Gateway is 192.168.1.1, and that the DNS table is populated. If not, the problem is either the NIC (misconfigured, bad drivers, or simply bad NIC), or a bad cable, or both. Every once in a while you see a defective port on the router, so it is worthwhile swapping the LAN port on the router with the known good port of the other machine to see if the problem transfers to the once good machine.
 
Has this situation ever been resolved? I have almost an identical situation. 3 computers, 2 with XP home and 1 with win2k pro, Linksys WRT51AB connected to a cable modem. All three computers can connect to the internet just fine but cannot see each other.

This suggests among other things that the NIC's and switch ports are functioning. I have made every effort to ferret out any firewall components and disable them, all to no avail.

Any ideas?

Thanks

Carl
 
Carl,

I know this is considered bush league, but if you have done everything right (this checklist by Steve Winograd is a good one:
Then install Netui on all workstations. I know Microsoft has tried to downgrade the use of Netbui with XP. For experienced LAN guys this is just silly. There are intractible situations where Netbios over TCP/IP just does not work. cf.
Install Netbui on al workstations. For XP you can use the Win2k netbui stack if you choose.

If, after 20 or so minutes, the workstations do not fully populate your Network Neighborhood, with Netbui installed on all clients, you have a hardware problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top