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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New work XP laptop won't connect to the web

Status
Not open for further replies.

DukeSSD

Technical User
Jun 28, 2004
792
GB
Hi All,
I've just got a new XP laptop. My home lan is 192.168.0.x, ADSL router with DHCP.
I've not had a problem connecting before but this machine won't see the web and the vpn software won't connect either.
I'm stumped, don't know where to look. I have a few home machines, 98, 2k and XP but this one I can't work out.
It connects, wireless, in hotel / airport WiFi areas but wired or wireless it won't connect at home.
Any ideas please.
Let me know what info might help, I have Admin rights.

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

Just after boot:

C:\Documents and Settings\user>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP DukeSSD:epmap 0.0.0.0:0 LISTENING
TCP DukeSSD:261 0.0.0.0:0 LISTENING
TCP DukeSSD:microsoft-ds 0.0.0.0:0 LISTENING
TCP DukeSSD:3460 0.0.0.0:0 LISTENING
TCP DukeSSD:3465 0.0.0.0:0 LISTENING
TCP DukeSSD:1040 0.0.0.0:0 LISTENING
TCP DukeSSD:5180 0.0.0.0:0 LISTENING
TCP DukeSSD:netbios-ssn 0.0.0.0:0 LISTENING
UDP DukeSSD:401 *:*
UDP DukeSSD:402 *:*
UDP DukeSSD:microsoft-ds *:*
UDP DukeSSD:isakmp *:*
UDP DukeSSD:4500 *:*
UDP DukeSSD:ntp *:*
UDP DukeSSD:1900 *:*
UDP DukeSSD:62515 *:*
UDP DukeSSD:62517 *:*
UDP DukeSSD:62519 *:*
UDP DukeSSD:62521 *:*
UDP DukeSSD:62523 *:*
UDP DukeSSD:62524 *:*
UDP DukeSSD:ntp *:*
UDP DukeSSD:netbios-ns *:*
UDP DukeSSD:netbios-dgm *:*
UDP DukeSSD:1900 *:*

After firing up the vpn client

C:\Documents and Settings\user>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP DukeSSD:epmap 0.0.0.0:0 LISTENING
TCP DukeSSD:261 0.0.0.0:0 LISTENING
TCP DukeSSD:microsoft-ds 0.0.0.0:0 LISTENING
TCP DukeSSD:3460 0.0.0.0:0 LISTENING
TCP DukeSSD:3465 0.0.0.0:0 LISTENING
TCP DukeSSD:1040 0.0.0.0:0 LISTENING
TCP DukeSSD:5180 0.0.0.0:0 LISTENING
TCP DukeSSD:netbios-ssn 0.0.0.0:0 LISTENING
UDP DukeSSD:401 *:*
UDP DukeSSD:402 *:*
UDP DukeSSD:microsoft-ds *:*
UDP DukeSSD:1053 *:*
UDP DukeSSD:1054 *:*
UDP DukeSSD:1055 *:*
UDP DukeSSD:1056 *:*
UDP DukeSSD:1057 *:*
UDP DukeSSD:ntp *:*
UDP DukeSSD:1900 *:*
UDP DukeSSD:62515 *:*
UDP DukeSSD:62517 *:*
UDP DukeSSD:62519 *:*
UDP DukeSSD:62520 *:*
UDP DukeSSD:62521 *:*
UDP DukeSSD:62522 *:*
UDP DukeSSD:62523 *:*
UDP DukeSSD:62524 *:*
UDP DukeSSD:62525 *:*
UDP DukeSSD:ntp *:*
UDP DukeSSD:netbios-ns *:*
UDP DukeSSD:netbios-dgm *:*
UDP DukeSSD:1900 *:*
 
Looking at ipconfig I have a 192.168 address, a class C network, the gateway is the ADSL address and the DNS server seems OK, I can ping ME, the router and the DNS server.
But I can't ping anything else on the web, I can't resolve addresses (ping -a) nor can I ping hostnames and not even AOL IM can connect, and I've seen that connect with all sorts of configuration problems before.
ARGHHHHH!
 
Half the battle won, the BT ADSL DNS server configured on the router would not respond to DNS lookup requests, although it did respond to nslookup enquiries. (all my other machines have DNS servers configured locally.)
So all working wired, just the wireless connection to sort out now.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top