Cannot browse/email/IM, but can ping (did search) 2

[bmrtx78]

http://www.tek-tips.com/viewthread.cfm?SQID=860518&SPID=584&page=1

Sorry to post a link to another thread, but I put it up over in Dial-up. This forum however seems to be a more appropriate spot for it.

I'm really lost on what to do about this system. Help, please! My sanity thanks you.

 

[bmrtx78]

I have just tried the Winsock fix, and it did not help. I have run IPconfig and here are my results:

Windows IP Configuration
Host name....citadel
Primary DNS Suffix....blank
Node Type...Unknown
IP Routing enabled....No
WINS Proxy Enabled....No
PPP adapter EV1:
Connection SPecific DNS Suffix....:Blank
Description.....:WAN (PPP/SLIP) Interface
Physical Address....00-53-45-00-00-00
DHCP Enabled....No
IP Address....216.40.208.143
Subnet Mask...255.255.255.255
Default Gateway..216.40.208.143
DNS Servers...207.218.192.38
207.218.192.39
Netbios over TCP/IP...Disabled

I am about a day or two away from formatting and doing an install of XP Pro. I'm sure I'll have just as many problems with it, but it's available to me. This is ridiculous that this has happened twice now.

 

[smah]

Might I ask how you arrived at this configuration? The first thing that I noticed is that your machine's IP address is the same as your gateway.

 

[Grenage]

Smah,
Is that not normal for a stand-alone machine with a dialup?

bmrtx78,
Have you tried switching to alternate DNS servers as a quick test? (eg. 158.43.240.3, 158.43.240.4).

 

[bmrtx78]

Yes, I have tried two other DNS servers, still no go. I am using the same internet connection on the laptop I'm currently on, so I don't think it's something on the ISP end. Definately on my machine's end.

This is a stand alone system with dial-up, I normally run ZoneAlarm for the firewall. I have removed that, made sure the XP firewall was disabled, and made sure that ICS was disabled as well Just to be sure. The link in my first post points to a thread with more information on what I've already tried. I'm confused, and it seems that everyone I've called can offer no advice either. I'd rather not do a complete reinstall because I just reactivated this copy of XP after installing the new motherboard...getting tired of calling them. Thanks for the replies, let's keep them coming.

 

[smah]

Sorry, that arrangement may be normal - it's been so long since I've used dial-up that I don't really know. I just looked odd to me.

bmrtx78, I'm still curious are all these settings picked up by DHCP or are you setting them manually? Also, just to rule things out, it would be worthwile to follow faq608-4650 step by step.

I just thought of another thing....If you go throught the network connection wizard as if to create another dial-up connection, are there any connection choices that are dimmed or unavailable?

 

[bcastner]

Why is DHCP disabled on this connection?

 

[bmrtx78]

I'm not sure why it's disabled. From what little I know, I thought DHCP was disabled for dial-up. But this was done automatically, the only thing I changed was telling XP to redial automatically. How do I turn it on if it's supposed to be on?

 

[bcastner]

Right-click the dial up connection, Properties.
Highlight TCP/IP, and click the Properties button.
Click the radio button to "obtain an IP automaticly"

Save the changes.

 

[bmrtx78]

Ah ok. Yes, that is definately selected. I've also tried it with both automatic DNS and manual DNS, no joy. I've removed and reinstalled TCP/IP as well.

 

[bcastner]

See:

http://support.microsoft.com/?kbid=811259

Start with the section titled "How to Recover from Winsock2 corruption"

 

[bmrtx78]

BCastner,

Worked like a charm. Why is it when I ran the WinsockXPFix tool it didn't fix this? I followed the steps exactly. Or does it not address winsock2?

I just want to thank you again. I'm about to call the rep I spoke to at my ISP and inform him of what it took.

 

[bcastner]

The approaches are slightly different. WinsockFix essentially rebuilds the Winsock and Winsock2 registry stacks only. The latter approach I provided above reinitializes the protocol itself.

My favorite approach in stubborn cases:
. run WinsockFix. It gives you a clean registry for Winsock and Winsock2 keys;
. rebuild the protocol itself as the MS KB article suggests.

Personally, I follow again with WinsockFix, as it makes certain the the stack entries under the Winsock and Winsock2 keys are complete with 13 entries.

Glad you got it sorted.
Bill Castner