Post #70,818
12/25/02 4:08:27 PM
|
So wtf am I doing wrong
XP laptop. Install wireless card. Set up fixed ip networking (don't use DHCP inside...never felt like setting it up...will probably do so soon...but...
Set up gateway, dns, everything just like I have on all other windows versions.
Freakin thing won't connect. Can't ping gateway.
After a couple of tries...get it to see the other computers on the network ("see" them...no access to network shares)...still cannot ping gateway from the command prompt...still cannot access internet.
XP...I hated it before I got started...glad to see, as a pessimist, I have not been dissappointed.
You were born...and so you're free...so Happy Birthday! Laurie Anderson
[link|mailto:bepatient@aol.com|BePatient]
|
Post #70,837
12/25/02 6:42:20 PM
|
can you ping localhost and local address?
sounds like if you can see the other boxen you might be getting the net stuff up but not the ip stack. Rip everyother stack out of the setup except for that ip stack on that card.
thanx,
bill
will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]
You think that you can trust the government to look after your rights? ask an Indian
|
Post #70,848
12/25/02 9:53:59 PM
|
Does the router need wireless card's serial number?
Alex
"No man's life, liberty, or property are safe while the legislature is in session."\t-- Mark Twain
|
Post #70,855
12/25/02 10:43:28 PM
|
Router is a linux box
and I turned off the security on the network. Not really paranoid.
I have several other things to try...but first will check the stack per box's suggestion.
First XPerience. Not liking it. I've got 95, 98, and 2k and a half dozen different linux installs to work with this setup in a combined total of about 10 minutes.
2 hours with XP and still no joy. So...bag the wireless for now...plug it in and see if I can get it working that way...then back to the wireless setup.
Entry in dictionary next to PITA....Bill Gate's latest OS.
You were born...and so you're free...so Happy Birthday! Laurie Anderson
[link|mailto:bepatient@aol.com|BePatient]
|
Post #70,865
12/26/02 12:01:16 AM
|
XP = 'Extra Pain' (sometimes 'Extreme Pain')
You can't get XP Home Edition to talk to FacetWin or a Samba server because the EnablePlainTextPassword parameter doesn't actually work.
I understand some people have gotten Home to work with a Samba server set up just right with encrypted passwords, so I gues I'm going to have to learn to implement that. Of course, if you've got a domain controller or Active Directory, Home is out of the question.
Nor will Home work with certain Cleint Server database applications on NT or 2000 servers, even though there's no domain.
Of course, everyone who buys a notebook computer gets it with Home, then brings it to work and expects it to function fully on their network. This is just another of Microsoft's schemes to sell two copies of Windows for every computer.
[link|http://www.aaxnet.com|AAx]
|
Post #71,051
12/27/02 2:32:59 AM
|
Re: XP = 'Extra Pain' (sometimes 'Extreme Pain')
A multiboot computer on every desktop! It's my vision!
The expanded directories of driver packages are getting comical. 95,98,ME,NT,2000,XP.
Let's see if we can list them in order:
1) Windows 1.0 - the only usable program was "Clock".
2) Windows 2.0 - the only usable program was "Clock", but you could have a game of "Reversi" partially obscure the clock.
3) Windows 3.0 - sorry 3.1 - this is a famous Microsoft trick - they sell people broken stuff and then fix it almost immediately, a tactic that occurs over and over again.
"Clock" is better than ever - big grey letters for testing that new video driver acceleration and graphi- oh oh, the clock stopped.
4) Windows 4.0 - 95 - oops! It's broken, sorry! We made 95b just for you! See how reponsive tech support is?
For some strange reason, Microsoft decides to cede the "Clock" market to OS/2, reducing the app to a small afterthought in the bottom corner. For an extra fee, you can purchase the "Clock Migration Resource Kit" which transfers the license, code, and runtime libraries for the 3.1 "Clock" to your new installation. There is a special 16bit mode specifically made for backward "Clock" compatibility.
5) Meantime, in the colonies, we have...
Windows NT 1.0 - er - 3.1. Oops, darn it all! It's broken! Here's 3.51! See how responsive we are?
The main advantage of Windows NT 3.51 is that is can run a shitload of "Clocks", each in its own Windows 3.1 emulation mode - oh no, the clocks are all slowing down...hmmm.
Etc. etc.
Is two per desktop enough?
5) Windows
-drl
|
Post #71,074
12/27/02 10:34:58 AM
|
email this post to BG ROFL!!!
will work for cash and other incentives [link|http://home.tampabay.rr.com/boxley/resume/Resume.html|skill set]
You think that you can trust the government to look after your rights? ask an Indian
|
Post #74,455
1/14/03 3:11:01 PM
|
Accessing SAMBA server is easy
set up encrypted passwords in SAMBA by using this lines in the smb.conf file:
encrypt passwords = yes
smb passwd file = /etc/smbpasswd
then add each user onto the server with smbpasswd -a username password
I have this setup at home (with two firewalls between it and the outside world of course)
~~~)-Steven----
"I want you to remember that no bastard ever won a war by dying for his country.
He won it by making the other poor dumb bastard die for his country..."
General George S. Patton
|
Post #70,851
12/25/02 10:01:33 PM
|
Re: So wtf am I doing wrong
This is just a guess, but on Windows it must be similar to the way they treat the infrared port - namely, it's a particular way of encapsulating NetBIOS with a special protocol - on infrared this is "fast infrared protocol". You can then ping by machine name, and WINS resolves it. As far as I know, you can't directly bind IP to the infrared port.
Once the special protocols are in place, it's like any other Windows networking connection.
-drl
|
Post #70,872
12/26/02 12:49:24 AM
|
You're using XP - that's what you're doing wrong. :-)
"Ah. One of the difficult questions."
|
Post #70,880
12/26/02 1:24:20 AM
|
Re: So wtf am I doing wrong
Check out your IP Configration.
Drop to a DOS Prompt, or rather choose the Start Button, and then "Run" and then type in "CMD" and then hit enter.
Bingo:
c:\\Windows\\desktop\\>
Now type in:
ipconfig /all > myip.txt
Look at the myip.txt file, and then see what IP it has configured. If it is 192.168.0.2 with a Netmask of 255.255.255.0 and your server is 192.168.0.1 with a netmask of 255.255.255.0 then you are all set.
If your IP address does not look the same as the one on your server, it will not ping! You may have to set this manually. DHCP may not be working for some reason.
Good luck, tell us if the IP matches the same series as the one on the server, etc.
For an Alternative Nearly To Imitate IWETHEY please visit [link|http://pub75.ezboard.com/bantiiwethey|the ANTIIWETHEY Board]
providing an alternative to IWETHEY since December 2002
|
Post #70,881
12/26/02 1:27:25 AM
|
Wait, I just had an idea
did you turn on the NetBIOS option? It is automatic and disabled by default, change it to Enabled and it should be able to connect to the other systems on your network. My brother had a problem like that and turning on the NetBIOS over TCP/IP worked with Non-XP machines.
Also did you turn on any of the "FIrewall" or security settings for the LAN connection? Chances are you may have shut down certain ports. Try an enable all on all ports to see what happens.
For an Alternative Nearly To Imitate IWETHEY please visit [link|http://pub75.ezboard.com/bantiiwethey|the ANTIIWETHEY Board]
providing an alternative to IWETHEY since December 2002
|
Post #70,907
12/26/02 9:38:56 AM
|
Re: So wtf am I doing wrong
My boss asked me tohelp his son with wireless setup
turned out that without the newest drivers (it said XP on the box, etc.) it would not work
A
Play I Some Music w/ Papa Andy
Saturday 8 PM - 11 PM ET
All Night Rewind 11 PM - 5 PM
Reggae, African and Caribbean Music
[link|http://wxxe.org|Tune In]
|
