US Telco Support > AT&T > AT&T Southwest > Help needed! Can only ping, no http, etc.

Help needed! Can only ping, no http, etc.

Have you configured your browser(s) to use the LAN instead of a dial-up connection?

reply to activinet
First off, welcome to the SwBell Forum!

Now, have you logged in to the SwBell server first and added in your username and password. You can't access the "net" without first registering. If you look in your paper work that came with the install help cd, you will see an address that has "https" in it. You need the "s" in order to get to the site. Once you register and set your EnterNet 300 login and password to the same, you should be alright. Keep in mind, you need to login with SwBell's service to get to the net! If that does not work, post back and we'll dig deeper.
--
-- (sing) I owe! I owe! So off to work I go!

reply to powerhog
Yes, my browsers are configured for LAN.

I have not registered my own username yet, because also according to the install guides, one should have no trouble going to »secure.swbell.net/dsluniversal with the "dslreguser" login. I do have trouble doing this. (Not trying to be obstinate, but having no dsl registered username should have nothing to do with my dialup connection at a different ISP.)

I read in another thread that I can register from any Internet connection, but I don't want to do that, may be a (slim) bargaining chip with SWB.

It bugs me that my trusty web browsers won't work with the dialup connection to ev1.net either. I know it had to have something to do with a bad software install, either the Westell or the Enternet, I just don't know where to look.

Well, it could be an MTU problem if it is set too high. If you tweaked your system for ISDL and had a DHCP then your MTU may be set at 1500. You can download DrTCP from the Tweak FAQ and see what it is set too and change the value if too high. Try 1450 to start with, there should be no problem with that.

Yes you should be able to get to secure site to register fairly easily.

Check on the MTU first, then maybe on to more drastic measures.

reply to activinet
Oh, gotcha. Do you have any previous PPPoE software installed on your system? What about "tweaking" programs installed on you machine? If you picked a bad one at some time then that could cause problems. What all protocals to you have bound to your NIC? Right now I'm just throwing our suggestions because I'm kinda at a loss. I'll be paying attention to this thread so I can see how it is resolved!
--
-- (sing) I owe! I owe! So off to work I go!

reply to Flippant
In reply to Flippant and DaSneaky1D:

DrTCP told me MaxMTU for the Intel Pro100 NIC was 1492, so I reset it to 1450, rebooted, tried both Enternet and dialup again. Neither method showed a difference in results. (As for other DrTCP settings, the TcpRcvWin = 65535 and the TTL = 64) (Did not look at or change any MTU for the NTS PPPoE adapter)

I already had DrTCP, which I used last year to tweak the Northpoint IDSL. As for protocols, all I have bound to the adapters is TCP/IP. Northpoint IDSL was a static IP address, so I never needed, nor had, PPPoE on this machine before.

Any other ideas, anyone? That Netscape error message has had me thinking that the SWB DSL software install did something "winsock-related" that was "bad". Does anyone know if/how I should investigate this? I already checked versions of "winsock" per the Win 98 troubleshooter. It checked out, but, there was one winsock-related file that I had on my PC that wasn't on the Win98SE disk (can't recall which and I'm not near the PC now).

Unfortunately the only thing that comes to mind is kind of drastic. First uninstall Enternet, then remove the NIC driver, install NIC driver, install Enternet with reboots between each.

quote:

---

As for protocols, all I have bound to the adapters is TCP/IP.

---

quote:

---

Northpoint IDSL was a static IP address, so I never needed, nor had, PPPoE on this machine before.

---

reply to activinet
Go to start-settings-control panel-add/remove programs. Double click on Internet Explorer. Click on Repair browser and reboot and retry. The winsock registry key could also be bad. You can also restore the registry to the day before you had the browser issues. Reboot the PC and hit F8 as it reboots to go into the boot menu and choose command prompt only. Then type scanreg /restore and you choose a back up from a day it was good. It restores the registry.

reply to Flippant
Flippant, I did all you suggest yesterday, in that order, to no avail. The NIC and PPPoE are bound. IE settings are as you suggest.

I didn't have the Northpoint IP in my network settings, and I have tried both "Obtain an IP address automatically", and also hard-coding one (192.168.0.1). I tried now with the 10.0.0.1 and it's no different.

I'm not sure what all my network settings should be, because the install guides gave no settings, and I can't go to the SWB website because I can't use my web browser. Talk about Catch-22!

Right now, for the Intel adapter I have 10.0.0.1 as IP and 255.255.255.0 as submask. I have "Obtain IP..." for the PPPoE adapter. I have "Disable WINS" checked for both. I have no Gateway for either adapter (should I have one?). I have "Enable DNS" checked for both, and I have the domain name as swbell.net, and I have the primary and secondary dns (151.164.1.8, 151.164.1.7, 192.5.5.241, as someone suggested in another thread). Netbios over tcp/ip is checked but the box is grayed out (not selectable). Bindings to "Client for Microsoft Networks". "Allow Binding to ATM is No for both adapters, and the bottom checkbox is unchecked.

Do the above look reasonable?

reply to activinet
Activinet,
Your situation sounds similar to the problems I had when first connecting to SBC DSL. To make a long story short, I was using the same NIC you have (although it was NEVER used before I got DSL). Things got worse when I used the SBC helpdesk. It turns out that after I replaced the NIC with an inexpensive Linksys card and uninstalling and reinstalling the Enternet 300 software (previously registered) I was able to connect. I would suggest that you take the advice of the experienced posters here at DSLR. If that fails all attempts try a different NIC card and see if that helps. We'll stay tuned. Good luck!
mb
(absorbing the wise advice at DSLR)

reply to activinet
Hmmm, sound mostly fine. Believe it or not, if you aren't doing home networking you can even kill the TCP/IP stack for the NIC and things will work fine, but that is another subject. Unfortunately on the machine I am using I have RASPPPoE and it is a bit different. But what you have sounds in the realm of being correct.

Unfortunately, I am running out of ideas. It sounds like you have a fair understanding of this stuff. Hopefully someone else using Enternet can check your network settings for correctness.

Before doing anything really drastic like fdisk, you might try uninstalling IE and Netscape (backup you bookmarks) or update IE. If something is wrong with the Winsock I believe a reinstall may fix it.

Good luck and let me know if you get it fixed. Don't think I have heard this particular problem before.

reply to activinet
Possibilities:

1) Your Intel Pro 100 NIC card may not be compatible with the Westell 516 because Westell 516 modem only support 10BaseT NIC card but not straight 100BaseT NIC card?? The included NIC that came with your Westell Modem is a 10/100 NIC card but not straight 100BaseT, however.

2) Just a side note on this for possible initial stall prevention, probably nothing to do with your problem:

192.168.0.1 private IP address uses subnet 255.255.255.0 for class C

But 10.0.0.1 is class A and should be subnet with 255.0.0.0

3) You don't need to use Enternet 300, use Raspppoe instead to create your DSL registration profile, it works the same way as Enternet 300 which will allow you to accomplish registration any way...

4) Start simple with just a video and a NIC card with everything else disabled via either CMOS or unplug...also start clean with Enternet 300 uninstall, NIC driver removed, TCP/IP stacks removed, etc..what IRQ was assigned to your Intel PRO 100 NIC card?

5) Last resort, have ASI dispatch a tech out to your prem and ask the tech to surf the net using his own Laptop with your Westell Modem, it could be that your line is wired to the wrong/bad DSLAM port(or wrong/bad RT VCI?)...just to see whether it's your problem or the network configuration side/line issues, etc...:(

Good luck..:)
--
me surf via me house netwire, FREE to do anything...

reply to activinet

said by activinet:

---

The Problem: Since getting sync last week, cannot do anything but "ping" or "tracert".

---

reply to Anon

said by NoHoP:

---

Possibilities:

5) Last resort, have ASI dispatch a tech out to your prem and ask the tech to surf the net using his own Laptop with your Westell Modem, it could be that your line is wired to the wrong/bad DSLAM port(or wrong/bad RT VCI?)...just to see whether it's your problem or the network configuration side/line issues, etc...:(

Good luck..:)

---

reply to activinet
Your Winsock files are corrupted. I've run into this before on some of my customers computers. This procedure can have a significant impact on the customer’s computer, but the need for this procedure seems to be showing up more and more. During the installation of the DSL line, sometimes the Winsock files become corrupted. Or they are corrupted to begin with. And sometimes, everything works fine for a period of time, and then the browser stops working. This is a procedure that many times will resolve the problem.

Before you start the editing procedure, It is always a good idea to make a Windows Start-Up disk, and to have a back-up copy of the registry.

Win98
(Customer Computer)
To restore damaged or corrupt Winsock files. The computer will connect with the PPPoE adapter, but the browser will not work. The same symptoms are seen using the analog modem. You can connect to your ISP, but the browser stalls, will not browse. The technician will be to connect and browse with their laptop.

REGISTRY EDIT

1. Remove Dial Up Networking From------ Control Panel
Add/Remove Programs
Windows Setup
Communications

(Reboot the Computer)

-Start-Run-Regedit

Registry Keys:

Expand:
HKey Local Machine

Expand:
System

Expand:
Current Control Set

Expand:
Services

Under Services, Delete the following Keys:
Winsock
Winsock2

Under Services, expand VXD.
Under VXD, delete the following Keys:
AFVXD
DHCP
MSTCP
WINSOCK
WINSOCK2


Rename in the "c:\windows\winsock.dll" to "winsock.asi"

After the Registry has been edited, go back and re-install Dial-Up Networking to restore your Winsock files to original condition. You will need the Win98 O.S. disk, unless the O.S. is on the hard drive.
I have duplicated this procedure in WinME, but after I uninstalled Dial-Up Networking, the computer would always reboot in Safe Mode, until I re-installed Dial-Up Networking.

One thing to consider with a new installation on a WinME machine- you can create a restore point before you start the installation. This will allow you to return the customer’s computer to its previous condition. (Pre-Install).

After this procedure, you may have to un-install your PPPoE software, and re-install it.

I would also recommend changing your NIC as the Westell is only 10meg. I'm not sure if it will work with a 100m only card.

Good Luck!

--
To be or not to be, only the router knows!

Ken

dsljock,
You hit the mark, thanks a bunch! I followed your procedure, and after the re-install of DUN I was able to log in as dslreguser, register, and be on my way. Thanks a bunch, I had a feeling it had to do with a bad software install, either for the modem or Enternet, because it screwed up my dialup ability as well.

I appreciate all the help and support I received on this board, and I hope to return the favors soon (and often).

First test shows 578/79, so I'll be doing some tweaking, as I'm within (I think) 5000 feet from the RT. Thanks again, everyone!

Glad I was able to help. After the tweaks you should be above 1100 for sure with just the RWIN tweak. good luck and glad it worked.

dsljock, Thank goodness you came along with some timely information to get this one fixed. This is the first time I have heard of this happening, but you can bet I bookmarked ot for the next time. Nice call!

activinet, Very happy to hear that you are up and going. Good luck and happy surfing!