MS Network logon and IE network access bugs(?)

[Gafling]

I should probably know this but I cannot resolve this issue.

I have a W98 computer configured for MS networking over TCP/IP; works fine. However the user has mentioned that when they do NOT successfully enter their user name and password in the MS Network Logon window or if they click the 'x' to bypass the logon procedure, they can STILL GET ON THE INTERNET with IE5.5.

It is my understanding that if a user fails to logon to the LAN correctly, only resources on the user's computer are available to them. IE5 or any other program that would access the LAN should fail. This is apparently not the case.

So the question is, how do I isoloate the W98 box when a network logon is NOT done correctly? I appreciate any help.

 

[deh]

Are you using static IPs or DHCP? Regardless, what looks like is happening is even though you don't logon to the server your workstation still has assigned IP configuration. (Default for DHCP i believe is 3 days). So the machine knows where the gateway is thus providing internet access (address of your router).
Winipcfg should verify this.
A proxy can accomplish what you would like. MS Proxy is discontinued but you can use ISA.

Check out MS's website or you can use a multitude of products like Wingate (

http://www.wingate.com).

HTH
Dan

 

[Gafling]

Thanks for the response. The machines in question use static IP addresses and also we use WinGate for firewall protection and as a proxy server. My point is that I don't believe IE should even try to access the LAN if the LAN login has not been completed successfully.

Is there an option in IE to check for a LAN login? Or should I make a script that performs that function? Any other suggestions?

 

[mainegeek]

Yes, under connections, settings.

 

[Gafling]

mainegeek, being VERY familiar with the properties of IE in general and LANs in particuler, I am unaware of a setting that addresses my dilemma. I would appreciate any SPECIFIC information you may have. Or if you know of another solution, please share with us.

 

[mainegeek]

Are you using a dial-up connection? and does the workstation in question have a dial-up modem installed in it?

 

[Gafling]

Good questions ... more information is needed.

The workstation is on a small LAN serviced by a server that is connected to a cable modem. The server has two NICs, one connected to the local LAN, the other connected to the cable modem. The local LAN computers use static addresses and are set up to use the server as a proxy. All of these computers use Outlook or Outlook Express for mail service and IE5.5 for surfing.

The server also has a static address on the local LAN NIC but uses DHCP to contact the ISP thru the cable modem. As mentioned before, the server runs Wingate firewall software. The dual NIC configuration makes the local LAN virtually invisible to the 'net. Also the local machines use a non-routable IP address scheme.

All this is somewhat moot in my opinion anyway. I maintain that, at the workstation, if the user has failed to log on to the network successfully, whether it is Microsoft Networking, Novell or some other, IE should NOT be able to contact the ISP. It should be as if the RJ-45 plug was not connected.

Thanks for your time ...

 

[mainegeek]

On the computer in question, I believe that the Default Gateway and the DHCP should have the IP of the LAN NIC that is on on the Server. This should at least force a log in when they attempt to access the internet.

 

[mainegeek]

You also might want to check and be sure that the
Tcp/Ip in Network Settings on WS in question is only binded to Client fpr MS Networks.