Question Locked

Home network issues(windows XP) via Billion BiPac 7100 router

0 helpful
13 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi there, here is my issue:

currently i am a student and theres four of us(students) in this dorm, wer've all got our PC's connected via a Billion Bipac 7100 router (4- port), we all run windows XP (some of us have home, i have Pro myself). we have each assigned ourselves IP's from the range of 192.168.1.1(me) to 192.168.1.4 (the 4th student). we have tried to set up a network with the "set up home or small office netork" wizard, we have all named our PC's(no duplicate names) and have all choosen the same workgroup(MSHOME), but i can access some files of some of the guys PC but they cant access mine and visa verca, we are all sharing a folder and made them public, but still we cant access each others folders, i keep getting the following error messages in my even viewer as well:

event ID: 8003
error message
MrxSmb
The master browser has received a server announcement from the computer ETL that believes that it is the master browser for the domain on transport NetBT_Tcpip_{4498E01E-603E-4C47-8DA1. The master browser is stopping or an election is being forced.

and..
event ID: 4321
error message
NetBT
The name "MSHOME :1d" could not be registered on the Interface with IP address 192.168.1.1. The machine with the IP address 192.168.1.3 did not allow the name to be claimed by this machine.

and..
event ID: 8032
error message
browser
The browser service has failed to retrieve the backup list too many times on transport \Device\NetBT_Tcpip_{4498E01E-603E-4C47-8DA1-B55BBD209DD7}. The backup browser is stopping.

These messages practically FLOOD my event viewer, were all connected correctly(physically that is the cables), we are all on the same workgroup, were all assigned individual IPs, we are all on the same subnet(255.255.255.0), we are all sharing folders, we are all on the same workgroup(MSHOME), we have all named our PC's, yet we cannot access each others folders etc..

13 replies

by shawn

Go to my website and look at the "Networking between XP Pro and XP home" article at the bottom of the page. I found that solution here and it works so weel I posted there. If the original author would send me an email I would like to put credit to him/her there as well.

by shawn

What is the address of the router?, can you send me a copy of the CMD- [ipconfig /all] and a [netstat -a]?

by stonemethod

Hey shawn thanks for your reply, this is the result of a ipconfig/all:

Windows IP Configuration

Host Name . . . . . . . . . . . . : xen
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SiS 900-Based PCI Fast Ethernet Adap
ter
Physical Address. . . . . . . . . : 00-17-31-51-C5-5E
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::217:31ff:fe51:c55e%4
Default Gateway . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 58.28.135.254
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-FB-F8-C5-E3-69-9C
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 2001:0:4136:e38c:0:fbf8:c5e3:699c
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-01-01
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.1%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

and this is the netstat-a:

C:\>netstat -a

Active Connections

Proto Local Address Foreign Address State
TCP xen:echo xen:0 LISTENING
TCP xen:discard xen:0 LISTENING
TCP xen:daytime xen:0 LISTENING
TCP xen:qotd xen:0 LISTENING
TCP xen:chargen xen:0 LISTENING
TCP xen:epmap xen:0 LISTENING
TCP xen:microsoft-ds xen:0 LISTENING
TCP xen:3306 xen:0 LISTENING
TCP xen:1030 xen:0 LISTENING
TCP xen:1042 xen:0 LISTENING
TCP xen:1048 localhost:1049 ESTABLISHED
TCP xen:1049 localhost:1048 ESTABLISHED
TCP xen:1051 xen:0 LISTENING
TCP xen:1053 xen:0 LISTENING
TCP xen:1058 localhost:1059 ESTABLISHED
TCP xen:1059 localhost:1058 ESTABLISHED
TCP xen:10110 xen:0 LISTENING
TCP xen:netbios-ssn xen:0 LISTENING
TCP xen:1084 by2msg2104613.phx.gbl:1863 ESTABLISHED
TCP xen:1171 jp-in-f99.google.com:http ESTABLISHED
TCP xen:1184 c17-b2b-xw-lb.cnet.com:http ESTABLISHED
TCP xen:1185 63-147-82-88.dia.static.qwest.net:http ESTABLIS
HED
TCP xen:1186 63-147-82-88.dia.static.qwest.net:http ESTABLIS
HED
TCP xen:1195 c17-b2b-xw-lb.cnet.com:http TIME_WAIT
TCP xen:1196 c17-dw-xw-lb.cnet.com:http TIME_WAIT
TCP xen:1197 c17-dw-xw-lb.cnet.com:http TIME_WAIT
TCP xen:1198 c17-b2b-xw-lb.cnet.com:http TIME_WAIT
TCP xen:1199 c17-dw-xw-lb.cnet.com:http TIME_WAIT
TCP xen:1200 c17-dw-xw-lb.cnet.com:http TIME_WAIT
TCP xen:echo xen:0 LISTENING 0
TCP xen:discard xen:0 LISTENING 0
TCP xen:daytime xen:0 LISTENING 0
TCP xen:qotd xen:0 LISTENING 0
TCP xen:chargen xen:0 LISTENING 0
TCP xen:epmap xen:0 LISTENING 0
UDP xen:echo *:*
UDP xen:discard *:*
UDP xen:daytime *:*
UDP xen:qotd *:*
UDP xen:chargen *:*
UDP xen:microsoft-ds *:*
UDP xen:isakmp *:*
UDP xen:1026 *:*
UDP xen:1033 *:*
UDP xen:1061 *:*
UDP xen:1107 *:*
UDP xen:3544 *:*
UDP xen:4500 *:*
UDP xen:ntp *:*
UDP xen:1080 *:*
UDP xen:1102 *:*
UDP xen:1166 *:*
UDP xen:ntp *:*
UDP xen:netbios-ns *:*
UDP xen:netbios-dgm *:*
UDP xen:router *:*
UDP xen:1031 *:*
UDP xen:echo *:*
UDP xen:discard *:*
UDP xen:daytime *:*
UDP xen:qotd *:*
UDP xen:chargen *:*

C:\>

by shawn

Networking XP Professional with XP Home
The first step is to get your PC's connected, I personally recommend using a router, it is by far the easiest way to do this. Make sure you give each PC a unique name in the network. To change the Computer Name, right-click My Computer, and then click Properties, click on the Computer Name tab, enter in the name then hit Apply. While you are here, you should also place your PC's in the same Workgroup, although this is not necessary, you can change that here, I use 'homenet' for my small home network. When you are done hit OK.

Now you need to make sure that you have NetBIOS over TCP/IP enabled on all the PC's in the network. Open the Network Connections folder, right-click the local area network connection and click Properties, double click Internet Protocol (TCP/IP). Click Advanced button then on the WINS Tab, click the Enable NetBIOS Over TCP/IP button.

The next step is necessary on XP Pro to allow XP Home to connect to it. XP Home uses Simple File Sharing in which all authentication is done via the Guest account. For XP Pro to allow this you need to modify a Group Policy to allow blank passwords. Go to the Start Menu and click on Run. Type in gpedit.msc and click OK. Navigate to Computer Configuration / Windows Settings / Security Settings / Local Policies / Security Options. Now double click on Accounts: Limit local account use of blank passwords to console login only. Change this to Disabled and click OK.

Thats it, share something on both PC's.

by justjoel99

Routers usually default to the first available IP address of the subnet. In your case, this is 192.168.1.1, which you have used for your computer. The other computers on the network cant figure out which device they are talking to, the router or your PC. Change your IP address to 192.168.1.5, and your problems should magically disappear.

by jvena1

After designating static IP's to the units on my network, that message stopped popping up. I was getting that error with my Vista laptop, apparently it kept trying to pull the IP that was being assigned to my Xbox 360. Once I assigned a static IP for all units given internet access, things work much better.

by stonemethod

Hey there, actually ive managed to solve the error messages by editing the group policies provided in shauns posts, however now we can see each other on the network - yet we cannot access each others shares, it just says that we dont have permisssion to view, ill try setting my IP to .5, thanks for the info

by shawn

need to right click on the shared folder and go to sharing, in make sure bot check marks are there, then go up one level to the parent folder and make sure its not set to private, did you enable netbios over tcp/ip? in the wins section of the advanced tcp/ip properties?, well anyway, win windos does something with networking that doesnt make any sense i have in the past created a user and password IDENTICAL on each machine, that seems to help, then i map a network drive using known pc names and shares with "log on with different user name" etc,, example: \\[PC-NAME]\[SHARE-NAME] and then click the "Connect using a different user name." then put in the common name and pswd.

by shawn

My typing in that last post was atrocious, My apology's.

by stonemethod

yup, ive made sure that netbios tcp/ip is enabled on all machines, and have edited the group policies like you said, although im still recieving the errors (Browser, and Mxsmb(i think thats what it was called)NetBT)

every machine on the network is windows home edition except for mine, which is Pro

but as far as maping the network drives, would i HAVE to log on as another user? for all machines? or will the current sessions be ok?

thanks again :)

by shawn

no, local user is fine, try this:
right click on "my network places" and properties, right click on the LAN in question, properties, "install" ... highlight "protocol" and click add.... click on "NWLink NetBIOS" add that to the mix and see if that helps

by shawn

that was only an alternative to the problem, you can add a "common" user to all machines and connect as... but usually not needed

This discussion is closed to new replies.