Non IP protocol for Windows networking

I have 2 computers (W2000 desktop and XP laptop ) connected to a W2003
server in my home LAN, all connected to a router for Internet access,
and all belonging to the same domain. I also have application level
firewall (Zone Alarm) on each machine, which is also used to lock
Internet access when desired.

I normally access the server using Remote Desktop. However when enable
the Internet lock feature on the server my Remote Desktop connection
also gets dropped. Is there anyway I can use a non-IP protocol for
secure LAN nwtworking, and IP for Internet access (via the firewall). I
used to use Netbeui for workgroup LAN networking, but I don't have that
protocol on my XP laptop, and I am not sure that a non-IP protocol works
Remote Desktop/Windows networking.

Appreciate any suggestions

K

I have not tested this but I suspect you can install NetBEUI on your systems
(for your Windows XP laptop see MS KB301041) then set the adapter protocol
bindings to use NetBEUI as the primary LAN protocol instead of TCP/IP. Of
course when you connect to the other Windows systems you must use their
computer name. All other IP applications like browsers should be
unaffected. Let us know if you get this working!

"kurb" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have 2 computers (W2000 desktop and XP laptop ) connected to a W2003
>server in my home LAN, all connected to a router for Internet access, and
>all belonging to the same domain. I also have application level firewall
>(Zone Alarm) on each machine, which is also used to lock Internet access
>when desired.
>
> I normally access the server using Remote Desktop. However when enable the
> Internet lock feature on the server my Remote Desktop connection also gets
> dropped. Is there anyway I can use a non-IP protocol for secure LAN
> nwtworking, and IP for Internet access (via the firewall). I used to use
> Netbeui for workgroup LAN networking, but I don't have that protocol on my
> XP laptop, and I am not sure that a non-IP protocol works
> Remote Desktop/Windows networking.
>
> Appreciate any suggestions
>
> K

Remote Desktop requires tcp/ip. If you have a decent router providing
firewall protection to your network I would not worry too much about using
all tcp/ip on the lan, particularly if you implement good patching
procedures for critical updates, use strong passwords, and have antivirus
protection that also scans ALL email attachments. There should be no problem
using Remote Desktop. I don't know what you mean by Internet lock feature on
your W2003 Server. If you mean the built in ICF firewall or any other
software firewall, just enable the firewall on that server to accept
incoming connections from port 3389 TCP. --- Steve


"kurb" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have 2 computers (W2000 desktop and XP laptop ) connected to a W2003
>server in my home LAN, all connected to a router for Internet access, and
>all belonging to the same domain. I also have application level firewall
>(Zone Alarm) on each machine, which is also used to lock Internet access
>when desired.
>
> I normally access the server using Remote Desktop. However when enable the
> Internet lock feature on the server my Remote Desktop connection also gets
> dropped. Is there anyway I can use a non-IP protocol for secure LAN
> nwtworking, and IP for Internet access (via the firewall). I used to use
> Netbeui for workgroup LAN networking, but I don't have that protocol on my
> XP laptop, and I am not sure that a non-IP protocol works
> Remote Desktop/Windows networking.
>
> Appreciate any suggestions
>
> K