PDA

View Full Version : re: protocol problems


amnesia
June 1st 03, 07:15 AM
Steve;

I've done everything you suggested, and I've finally got
the network places comming up automatically and the
gateway icon is staying put. Whew!!!!
A couple of things I noticed in my troubleshooting have
me a bit confused.

1) I was unable to connect to my network with file
sharing and microsoft client bound to TCP/IP. The only
way I could get it to work was to bind them to IPX/SPX
and enable netbios support for IPX/SPX. Most of my
reading suggested that you shouldn't bind file shareing
with TCP/IP anyway (for security reasons) Although I'm
using a router so it's probably a moot point.

2) I tried to install NETBEUI so that I could bind
sharing to it (as I read that it was a more efficient
protocol). I know that microsoft doesn't support it
anymore, but it is availabe on the CD and their web site
says it works. Anyway as soon as I installed it my
computer would freeze with a blue screen and I would need
to re-boot to safemode and uninstall NetBEUI in order to
restart windows!

I'd appreciate your comments on these two points.

Thanks
Amnesia

2)
>-----Original Message-----
>In article <2f4c01c3241f$5f8c1d30
>, "amnesia"
> wrote:
>>Steve;
>>
>>Thanks for the thoughtfull comments.
>>I checked everything you suggested, and they were all
as
>>you said they should be. I even disabled/removed them
>>all and re-installed them to no avail.
>>Then I tried Gary Tsang's suggestion from the entry
>>above: "Why the Internet Gateway" (funny, that guy has
>>the gateway icon and wants to get rid of it!) Anyway,
I
>>disabled and reinstated the Up&p on my D-link router,
and
>>lo and behold, the Internet Gateway appeared in my
>>network connections. (thank you Gary!) An entry called
D-
>>Link router even appeared in my network places!
>>Unfortunately, I still don't have any of my shared
drives
>>etc in the network places.
>>
>>I'm almost where I want to be.
>>
>>Any more ideas?
>>
>>Thanks
>>Amnesia
>
>You're welcome, Amnesia.
>
>In My Network Places, click "Add a network place" and
follow the
>prompts to create a shortcut to a desired network place.
>
>To have XP create shortcuts automatically, click Tools |
Folder
>Options | View and put a check mark in the
box "Automatically search
>for network folders and printers".
>
>If that doesn't do the job, I've written a web site that
should help
>you get the network places to appear:
>
>Windows XP Network Troubleshooting
>http://www.practicallynetworked.com/sharing/troubleshoot
>
>Please pay particular attention to these sections:
>
>1. Firewalls: Permanently disable XP's built-in
Internet Connection
>Firewall on local area network connections -- it's for
use only on a
>direct modem connection to the Internet. Disable and un-
install all
>other firewalls while troubleshooting.
>
>2. Protocols: Use only one for File and Printer
Sharing. If the
>network needs more than one protocol, unbind File and
Printer Sharing
>from all but one of them.
>
>3. NetBIOS over TCP/IP: Make sure that it's enabled on
all computers.
>--
>Best Wishes,
>Steve Winograd, MS-MVP (Windows Networking)
>
>Please post any reply as a follow-up message in the news
group
>for everyone to see. I'm sorry, but I don't answer
questions
>addressed directly to me in E-mail or news groups.
>
>Microsoft Most Valuable Professional Program
>http://mvp.support.microsoft.com
>.
>

Steve Winograd
June 1st 03, 08:12 AM
In article >, "amnesia"
> wrote:
>Steve;
>
>I've done everything you suggested, and I've finally got
>the network places comming up automatically and the
>gateway icon is staying put. Whew!!!!
>A couple of things I noticed in my troubleshooting have
>me a bit confused.
>
>1) I was unable to connect to my network with file
>sharing and microsoft client bound to TCP/IP. The only
>way I could get it to work was to bind them to IPX/SPX
>and enable netbios support for IPX/SPX. Most of my
>reading suggested that you shouldn't bind file shareing
>with TCP/IP anyway (for security reasons) Although I'm
>using a router so it's probably a moot point.
>
>2) I tried to install NETBEUI so that I could bind
>sharing to it (as I read that it was a more efficient
>protocol). I know that microsoft doesn't support it
>anymore, but it is availabe on the CD and their web site
>says it works. Anyway as soon as I installed it my
>computer would freeze with a blue screen and I would need
>to re-boot to safemode and uninstall NetBEUI in order to
>restart windows!
>
>I'd appreciate your comments on these two points.
>
>Thanks
>Amnesia

You're welcome, Amnesia. Here are my opinions on those questions:

1) If a network only works after adding another protocol, something is
wrong with the TCP/IP configuration. The other protocol is simply
covering up the problem. The most likely problems involve firewalls
and NetBIOS over TCP/IP, as I state on my troubleshooting web page.
Solving the underlying problem would eliminate the need for the other
protocol.

TCP/IP is perfectly safe for file and printer sharing when there's a
broadband router in the network. The router protects the network from
access by other Internet users.

2) Where did you see that NetBEUI is more efficient? I'd like to know
what it said. If someone has done network speed tests with different
protocols, I'd really like to see it.

I don't know why NetBEUI caused problems for you. Perhaps it wasn't
installed properly. It's hard to do it right in XP.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

amnesia
June 1st 03, 09:44 PM
Steve

I'm sure there's just something set wrong in TCP/IP to
not allow sharing. I'll just have to experiment a bit
more.

As for NetBEUI having advantages over TCP/IP, I don't
remember where I read it, but I don't think it was a
major deal.

On the issue of installing NetBEUI on XP Pro, all I did
was:

copy nbf.sys into the WINDOWS\SYSTEM32\DRIVERS\ directory
copy netnbf.inf into the WINDOWS\INF\ directory\
went to network connection properties and added NetBeui
protocol to my wireless adapter (all as per NetBEUI.txt
in WINDOWS\VALUEADD directory.

As soon as I go to do the bindings I get the blue screen
indicating a serious error (can't remember exactly what
it says) and the machine totally freezes!

What am I doing wrong?

Thanks
Jeff






>-----Original Message-----
>In article <049a01c32805$33688060
>, "amnesia"
> wrote:
>>Steve;
>>
>>I've done everything you suggested, and I've finally
got
>>the network places comming up automatically and the
>>gateway icon is staying put. Whew!!!!
>>A couple of things I noticed in my troubleshooting have
>>me a bit confused.
>>
>>1) I was unable to connect to my network with file
>>sharing and microsoft client bound to TCP/IP. The only
>>way I could get it to work was to bind them to IPX/SPX
>>and enable netbios support for IPX/SPX. Most of my
>>reading suggested that you shouldn't bind file shareing
>>with TCP/IP anyway (for security reasons) Although I'm
>>using a router so it's probably a moot point.
>>
>>2) I tried to install NETBEUI so that I could bind
>>sharing to it (as I read that it was a more efficient
>>protocol). I know that microsoft doesn't support it
>>anymore, but it is availabe on the CD and their web
site
>>says it works. Anyway as soon as I installed it my
>>computer would freeze with a blue screen and I would
need
>>to re-boot to safemode and uninstall NetBEUI in order
to
>>restart windows!
>>
>>I'd appreciate your comments on these two points.
>>
>>Thanks
>>Amnesia
>
>You're welcome, Amnesia. Here are my opinions on those
questions:
>
>1) If a network only works after adding another
protocol, something is
>wrong with the TCP/IP configuration. The other protocol
is simply
>covering up the problem. The most likely problems
involve firewalls
>and NetBIOS over TCP/IP, as I state on my
troubleshooting web page.
>Solving the underlying problem would eliminate the need
for the other
>protocol.
>
>TCP/IP is perfectly safe for file and printer sharing
when there's a
>broadband router in the network. The router protects
the network from
>access by other Internet users.
>
>2) Where did you see that NetBEUI is more efficient?
I'd like to know
>what it said. If someone has done network speed tests
with different
>protocols, I'd really like to see it.
>
>I don't know why NetBEUI caused problems for you.
Perhaps it wasn't
>installed properly. It's hard to do it right in XP.
>--
>Best Wishes,
>Steve Winograd, MS-MVP (Windows Networking)
>
>Please post any reply as a follow-up message in the news
group
>for everyone to see. I'm sorry, but I don't answer
questions
>addressed directly to me in E-mail or news groups.
>
>Microsoft Most Valuable Professional Program
>http://mvp.support.microsoft.com
>.
>

Steve Winograd
June 2nd 03, 12:25 AM
In article >, "amnesia"
> wrote:
>Steve
>
>I'm sure there's just something set wrong in TCP/IP to
>not allow sharing. I'll just have to experiment a bit
>more.
>
>As for NetBEUI having advantages over TCP/IP, I don't
>remember where I read it, but I don't think it was a
>major deal.
>
>On the issue of installing NetBEUI on XP Pro, all I did
>was:
>
> copy nbf.sys into the WINDOWS\SYSTEM32\DRIVERS\ directory
> copy netnbf.inf into the WINDOWS\INF\ directory\
> went to network connection properties and added NetBeui
> protocol to my wireless adapter (all as per NetBEUI.txt
> in WINDOWS\VALUEADD directory.
>
>As soon as I go to do the bindings I get the blue screen
>indicating a serious error (can't remember exactly what
>it says) and the machine totally freezes!
>
>What am I doing wrong?
>
>Thanks
>Jeff

Well, you've done the hard part by copying the NetBEUI files from the
CD to the right folders, one of which is hidden. I'm sorry, but I
don't know what the problem is.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

amnesia
June 2nd 03, 05:21 AM
Thanks for trying

Cheers


>-----Original Message-----
>In article <01bd01c3287e$9a2656a0
>, "amnesia"
> wrote:
>>Steve
>>
>>I'm sure there's just something set wrong in TCP/IP to
>>not allow sharing. I'll just have to experiment a bit
>>more.
>>
>>As for NetBEUI having advantages over TCP/IP, I don't
>>remember where I read it, but I don't think it was a
>>major deal.
>>
>>On the issue of installing NetBEUI on XP Pro, all I did
>>was:
>>
>> copy nbf.sys into the WINDOWS\SYSTEM32\DRIVERS\
directory
>> copy netnbf.inf into the WINDOWS\INF\ directory\
>> went to network connection properties and added
NetBeui
>> protocol to my wireless adapter (all as per
NetBEUI.txt
>> in WINDOWS\VALUEADD directory.
>>
>>As soon as I go to do the bindings I get the blue
screen
>>indicating a serious error (can't remember exactly what
>>it says) and the machine totally freezes!
>>
>>What am I doing wrong?
>>
>>Thanks
>>Jeff
>
>Well, you've done the hard part by copying the NetBEUI
files from the
>CD to the right folders, one of which is hidden. I'm
sorry, but I
>don't know what the problem is.
>--
>Best Wishes,
>Steve Winograd, MS-MVP (Windows Networking)
>
>Please post any reply as a follow-up message in the news
group
>for everyone to see. I'm sorry, but I don't answer
questions
>addressed directly to me in E-mail or news groups.
>
>Microsoft Most Valuable Professional Program
>http://mvp.support.microsoft.com
>.
>

Google