"Connected" is not checked.

[Blackcat]

Trying to use LNS on a new Laptop, Vista SP1, connecting via external modem.

I have tried changing the adapter selection in the option page but to no avail.

The only one which worked for a short time was the Network Monitor but this did not work after a reboot.

I have tried installing/uninstalling but this has not worked.

[Frederic]

The right network interface should be normally "Wan Miniport (IP) - Look 'n' Stop driver".
After you are connected to internet, if you select this interface and you press the "Apply" button, is your IP address properly displayed in the "Welcome" tab ?

Thanks,

Frederic

[Blackcat]

Hi Frederic,

No. The only time I have seen my IP address is when I chose the network adapter and as I stated above, this was only seen for a short time.

[Frederic]

Hi Blackcat,

Are you sure you pressed the Apply button (this is a common error...) ?

If there is no valid IP address for any network adapter selection, then I would like to know the result of the following utility after you are connected:
http://looknstop.soft4ever.com/Tools/AdaptList.exe

You can send me the result to lnssupport@soft4ever.com, if you don't want to display some private info here.
Or you can just put here the name of the adpater and tell us which one has the valid IP address.

Thanks,

Frederic

[Phant0m]

Not always do you see the External IP address, if you have something differ than 0.0.0.0 displayed on the Welcome screen, it's possible that it might be your Internal IP address and that Network adapter selection is a correct one.

[Blackcat]

I did press the apply button previously.

I will reinstall LNS, use the utility and post the info to you and the adapter here.

[Blackcat]

Well here we go;

LNS selected the network adapter when booted up and the Adapter list is shown below. The only one with an IP address against it was the last one, Dial-up connection; all the adapters had no IP address.

[Blackcat]

Manually selected Network adapter and now "Connected" was checked but IP address in LNS Window was slightly different to the one listed in the Adapter list; the last 3 digits were not the same.

But AGAIN on reboot, Connected is not checked and no IP address shown. Application filtering is working but nothing shown in the Logs.

Manually selected Network adapter again and Connected now checked. BUT I do not want to manually select the Adapter each time I go on-line.

[Frederic]

Anyway, I don't think it works properly when you select the Network Monitor adapter.
And the IP diplayed in the Welcome tab should be the same as the dial-up adapter shown by AdaptList tool.

It seems the dial-up adapter is not known by the driver.
I'm surprised it doesn't use the "Wan Miniport (IP)" interface and you have this dial-up interface (and additionally the MAC @ is 0, this is also a problem, even if dial-up doesn't have a real MAC @).
Did you install a special software package for the internet connection ?

If Look 'n' Stop is still installed, I would like to get the driver logs in the console window. The list of network interfaces known by the driver is displayed there when you press the Driver Logs button.

Thanks,

Frederic

[Blackcat]

-{ Quote: "Did you install a special software package for the internet connection ?" }-
Just for the drivers; Zoom USB Mini External.

-{ Quote: " If Look 'n' Stop is still installed, I would like to get the driver logs in the console window. The list of network interfaces known by the driver is displayed there when you press the Driver Logs button." }-
I could only find the following;

[Frederic]

-{ Quote: "Just for the drivers; Zoom USB Mini External." }-
Ok, this probably explains why it doesn't use the Windows usual "Miniport (IP)" interface.
-{ Quote: "I could only find the following;" }-
The console window is in Look 'n' Stop directly. In the options tab, tick the console window, and it will open. Then press the "Driver Logs" button.
What I need there is what you have between "FW:" and "FW1:".
For instance, something like this:
FW:
Driver Entry Win2k/XP/2003/Vista
Miniport réseau étendu (IP) - Look 'n' Stop Driver
Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller #2 - Look 'n' Stop Driver
NVIDIA nForce Networking Controller #2 - Look 'n' Stop Driver
FW1:

Thanks,

Frederic

[Blackcat]

Driver Logs as requested.

[Frederic]

Ok, thanks. So there is also no "Dial-up connection" adapter detected at the driver level.

When you select the "Wan Miniport (IP) Look 'n' Stop Driver", I understand the "Connected to internet" checkbox is not ticked and there is no IP address in the "Welcome" tab, but could you check the statistics ?
For instance, do the number of packets/bytes change when you open a Web page ?
Maybe "Wan Miniport (IP) Look 'n' Stop Driver" is anyway the right adapter to be selected and the problem is just to associate it with the "Dial-up connection".

Another check in windows configuration. From the network connections list:
203717

Ask the properties for the dialup adapter (with a right click on it) and open the "Networking" tab like this:
203718

Do you have a Look 'n' Stop driver there (like this screenshot) ?

Thanks,

Frederic

[Blackcat]

-{ Quote: "

When you select the "Wan Miniport (IP) Look 'n' Stop Driver", I understand the "Connected to internet" checkbox is not ticked and there is no IP address in the "Welcome" tab, but could you check the statistics ?
For instance, do the number of packets/bytes change when you open a Web page ?" }-
Yes, but only when Wan Miniport (IP) is selected BUT then I always see "Address not found" in my browser.

-{ Quote: " Another check in windows configuration. From the network connections list:
Ask the properties for the dialup adapter (with a right click on it) and open the "Networking" tab like this:

Do you have a Look 'n' Stop driver there ?" }-

Yes, LNS driver is there.

[Frederic]

Ok, thanks.
So, it is actually working properly at the driver level, and it's only at the application level there is a problem to associate "Wan Miniport (IP) - Look 'n' Stop driver" to the "Dial-up Connection" name.
I will send you a private patch with a workaround.

You get "Address not found" in your browser because the IP address is not found, and some rules (like the DNS one) require the IP address to allow the packets.
This also proves the filtering is working fine.

Regards,

Frederic