RAS and NETBEUI

[Guest]

This is directed toward Marc Reynolds or any other MSFT, but anyone that has a work around can
answer. I know that the NETBEUI protocol bound to RAS is no longer supported on Windows XP Pro
However I have an application that dials into another business, which has no desire to upgrade its' server OSes, that uses netbeui. I have been a dutiful MS customer and upgraded my servers and desktops to Windows 2K3 and XP. Unfortunately I cannot use this critical application any more. The business that owns the application basically told me to suck eggs when I explained the situation. Is there a configuration or kluge to fool the other side of the dial-up network to think that the XP is running netbeui?

 

[Bob Willard]

This is directed toward Marc Reynolds or any other MSFT, but anyone that has a work around can
answer. I know that the NETBEUI protocol bound to RAS is no longer supported on Windows XP Pro.
However I have an application that dials into another business, which has no desire to upgrade its' server OSes, that uses netbeui. I have been a dutiful MS customer and upgraded my servers and desktops to Windows 2K3 and XP. Unfortunately I cannot use this critical application any more. The business that owns the application basically told me to suck eggs when I explained the situation. Is there a configuration or kluge to fool the other side of the dial-up network to think that the XP is running netbeui?

The simple solution is to run NetBEUI under XP. It is not supported by M$,
but it does work under XP. If you have a real (OEM or retail) XP CD, then
NetBEUI is on the CD; if you only have recovery CD or no CD, then you'll need
to google for it. If you decide to install NetBEUI on your XP PC, make
sure you follow the directions exactly, or it will appear to install but
it won't work; the directions are in a .TXT file in the same folder with
the other NetBEUI files.

 

[Marc Reynolds [MSFT]]

While you are correct that you can install NetBEUI and it will work on XP,
it will NOT work over a RAS connection. I know of no way to get around this.
If the application is critical, perhaps you could use a Windows 2000 server
running Terminal Services and NetBEUI to dial the other business and the
clients could run the app via a RDP client session?

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.


has no desire to upgrade its' server OSes, that uses netbeui. I have been a
dutiful MS customer and upgraded my servers and desktops to Windows 2K3 and
XP. Unfortunately I cannot use this critical application any more. The
business that owns the application basically told me to suck eggs when I
explained the situation. Is there a configuration or kluge to fool the other
side of the dial-up network to think that the XP is running netbeui?

 

[Guest]

Bob and Marc
Thank you for your responces. To Bob; yes I was aware of the manual install of NETBEUI in XP and did perform it off the OEM disk. I, however, was not able to bind it to RAS and Marc mentioned. To Marc; your answer was about what I expected. It was less than desirable because it means that we'll have a handful of PCs that will have Windows 2k Pro and a few hundred PCs with Windows XP Pro which will compound problems with administration as well as politics ( Why do they get the newest desktop OS and I don't?, etc. ). Let me know if M$ is persuaded to change their minds about this inconvenience. =

Regards
Davi

 

[Marc Reynolds [MSFT]]

I doubt we will see a change to RAS to allow NetBEUI to work - ever. What
about the idea of a Windows 2000 Server w/terminal services making the RAS
connection with NetBEUI and then the XP clients can use RDP to connect to
the Win2K TS and run the app?? Will that work for you?

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

Bob and Marc,
Thank you for your responces. To Bob; yes I was aware of the manual

install of NETBEUI in XP and did perform it off the OEM disk. I, however,
was not able to bind it to RAS and Marc mentioned. To Marc; your answer was
about what I expected. It was less than desirable because it means that
we'll have a handful of PCs that will have Windows 2k Pro and a few hundred
PCs with Windows XP Pro which will compound problems with administration as
well as politics ( Why do they get the newest desktop OS and I don't?,
etc. ). Let me know if M$ is persuaded to change their minds about this
inconvenience. =<