Re: Strange networking issue
Posted by Monqui on
Sun May 16th 2004 at 3:12pm
Monqui
member
743 posts
94 snarkmarks
Registered:
Sep 20th 2002
Occupation: Poor College Student
Location: Iowa, USA
Ok, so it's not really creepalicious, but it's still annoying. Long story short, I have 2 PC's in my room, my main PC has 2 NIC's in it. I use one NIC to connect to the school network/get internet from, and that one works just dandy.
The other PC is my ghetto TiVo thingy, and it has 1 NIC in it. I am connecting these two PC's via a crossover cable (obviously, I'm using the other NIC in the main PC for this connection).
Now here's the problem. The TiVo doesn't have any problem connecting to the main PC, but I can't seem to access the TiVo from the main PC. The weird thing is, it responds to ping. I just can't pull anything useful up.
Now, I'm not looking to give internet access to the TiVo, I'm simply looking to be able to access it from the main PC.
If it helps at all, both boxes are configured with Default protocols, except for the NetBEUI protocol, which I installed on both boxes. Both boxes are in the same "Workgroup." The TiVo is running Win 98SE, and my main PC is running Win2k.
Any suggestions?
Re: Strange networking issue
Posted by scary_jeff on
Sun May 16th 2004 at 3:50pm
1614 posts
191 snarkmarks
Registered:
Aug 22nd 2001
I have had a lot of experience with this kind of thing, and windows 98 often experiences/causes problems like this when networking. I have found that instead of messing with settings for ages and ages (which can often end up with a network that 'sort of' works), the easiest thing is to leave the win2k machine as it is, then on the win98 machine:
o uninstall all the protocols and clients one by one
o uninstall the network card
o change the PCI slot the network card is in
o when the PC restarts, it will install the network card again; only install 'file and printer sharing', 'tcp/ip', and 'client for microsoft networks'
o set 'client for microsoft networks' as the default logon
o set up TCP/IP to whatever you are wanting it to do (auto on both machines, or specific IP/subnet for both machines), and set up file and printer sharing to 'allow other users to access my files'
o restart (stupid win98 always needs restarting), and share a folder
It should now work properly. You can try it first without swapping PCI slots, but this is the 'gauranteed work' method :smile:
Re: Strange networking issue
Posted by Monqui on
Sun May 16th 2004 at 4:16pm
Monqui
member
743 posts
94 snarkmarks
Registered:
Sep 20th 2002
Occupation: Poor College Student
Location: Iowa, USA
Hmmm... Could be a problem there- the win98 box's network card is an integrated one, so that may be a bit tough (and no, it's not possible to install one in a PCI slot (without completely hacking apart the back of the case).)
I'll try mucking around with uninstalling/reinstalling it though. Thanks!
Re: Strange networking issue
Posted by Monqui on
Sun May 16th 2004 at 5:08pm
Monqui
member
743 posts
94 snarkmarks
Registered:
Sep 20th 2002
Occupation: Poor College Student
Location: Iowa, USA
Ok, fixed the problem (just in case anyone actually cared). Turns out my vserver.vxd file was corupt, so the win98 box couldnt' share anything out. Oh well. Thanks again, though Jeff.
Re: Strange networking issue
Posted by scary_jeff on
Sun May 16th 2004 at 5:18pm
1614 posts
191 snarkmarks
Registered:
Aug 22nd 2001
hah, no problem :smile:
I never had that error before... do you think it would have been fixed by doing what I suggested? How did you find out that this file was in fact corrupted?
Re: Strange networking issue
Posted by Monqui on
Sun May 16th 2004 at 6:34pm
Monqui
member
743 posts
94 snarkmarks
Registered:
Sep 20th 2002
Occupation: Poor College Student
Location: Iowa, USA
Your solution would probably have fixed it- Windows would have to re-install that file from the disk when you enabled file sharing for the first time (again... so I guess it wouldn't be the first time, but whatever).
I assume that the file was corrupt, at least- I googled the issue, and several sites suggested that that particular file could have gone bad. So I took a shot and just manually re-installed it, and it worked fine.
I'm just not going to question it :smile: It works, that's all I care about.