Forum Home
Press F1
 
Thread ID: 47788 2004-08-05 20:49:00 IE6 problems - POrt 80 Conflicts - Telnet issues Jedi2002 (5973) Press F1
Post ID Timestamp Content User
258583 2004-08-09 00:47:00 Ive already talked to them - They reckon everything is sweet from there end. They seem to be as lost as i am. Jedi2002 (5973)
258584 2004-08-09 02:17:00 > sound a bit like your ISp is blocking you.....

Unlikely, if you haven't paid an account the ISP would stop you dialling in, rather than let you dial in and then sit there taking up a port with no traffic.

Well it sounds like no traffic at all. Try doing a Winsock Repair in WXP as follows:

How to Recover from Winsock2 corruption Windows XP:

This fix covers a reinstall of the TCP/IP protocol and WinSock socket layers to resolve "no traffic" problems on a computer as a result of a damaged socket layer, or protocols. This is often as a result of a damaged firewall application, botched SpyWare removal or similar.

As usual, I provide this with no express warranty etc - you botch it up then it's your problem. It's worked loads of times before with no problems, if you don't feel up to following the intructions get someone competent or a technician to perform them for you.

If swallowed, do not induce vomiting. Consume copious amounts of milk and consult your physician.

Step 1: Delete registry keys

* Open the Registry Editor from the run line. Start --> Run --> regedit --> ok
* Navigate to both of the following keys and then delete the key (folder):
* HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Winsock
* HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Winsock2
* Restart the computer

NB: It is important to restart the computer after deleting the Winsock keys. Doing so causes the XP operating system to recreate shell entries for those two keys. If this is not done, the next step does not work correctly.

Step 2: Install TCP/IP over top of the existing installation:

* Open the properties window of the network connection. Start --> Connect To --> Show All Connections --> Right-click the Connectoid --> Click Properties --> Select the Networking Tab
* Click Install
* Click Protocol
* Click Add
* Click Have Disk
* Type the path to the nettcpip.inf file and click OK. This should either be: c:\windows\inf or c:\winnt\inf (if you click browse, then attempt to browse to the \inf folder, it may not show up in the list as it is a hidden directory)
* You should now see "Internet Protocol (TCP/IP)" in the list of available protocols. Select it and click OK.
* Restart the computer

This fix will repair any damage to the TCP\IP stack, or WinSock socket layers on the computer. If you have any third-party firewall programs, content restriction programs or other similar pieces of software these will probably need to be reinstalled after performing this fix.

Try browsing now.
whiskeytangofoxtrot (438)
258585 2004-08-09 02:27:00 If you don't enjoy playing in the registry, LSP fix program (www.cexx.org) and Winsock fix program (members.shaw.ca)
An explanation on what LSP is here (www.cexx.org).
Take once and call in the morning :D
Pheonix (280)
258586 2004-08-09 02:32:00 Thanks everybody for your help - i'll try this tonight and see what happens Jedi2002 (5973)
258587 2004-08-09 11:16:00 Hmmmm -

Try ipconfig /flushdns and ping www.google.co.nz again. This'll make sure that it's your DNS that's a problem.

Then ping www.google.co.nz by IP Address. It is at the moment 64.233.167.199 . If that goes through, then your DNS is broken.

If that doesn't go through - either google's IP changed or your network is more so bung than previously suspected.

Do this if the reinstalls fail. What kind of internet connection do you have? Do you use a modem? ADSL Modem? Router?

Apologise if I missed something - but maybe your end is blocking traffic at a different level?

With most connections you should be able to set your DNS to auto - if possible to this. Then, if it doesn't help, try it manually.
Growly (6)
258588 2004-08-09 19:29:00 Hello All

Well it worked - Deleted those winsoc and winsoc2 reg folders and reinstalled TCP/IP protocol. All good Thanks to all of you who put forward suggestions.
Jedi2002 (5973)
258589 2004-08-09 20:04:00 And may the force be with you, Luke. Old Tom (5871)
1 2