Hi to all :) On /etc/diald.conf and at the parameter connect you MUST use the chat script and not a ppp script. Diald starts pppd by itself. When you put it at connect then diald thinks that this is the chat script and wait for the chat script to finish. pppd doesn't exit and the diald (using alarm system call) thinks that the chat script timed out. Look at the man page also to double check it. But if you cannot make it work there is an alternative method but that method requires that the ISP you use will drop the connection after some idle time that you will specify (at least this worked with my ISDN dial-up). Add a line at inittab like this: pd:23:respawn:/usr/local/bin/myppp where /usr/local/bin/myppp is a shell script like the following: #!/bin/sh exec pppd call my-isp where my-isp is the a file like the following in the /etc/ppp/peers directory: updetach /dev/ttyS1 115200 crtscts connect '/usr/sbin/chat -f /etc/ppp/YOUR-CHAT-SCRIPT' noauth ipcp-accept-local ipcp-accept-remote defaultroute lock asyncmap 0 idle 30 noipx demand persist holdoff 5 user YOURUSERNAME The above starts from init the pppd and creates the ppp0 interface but does not dial. When you ask something from the Internet only then the pppd starts dialing and connect to your ISP. The only problem I had at the begginig (and that is why you ISP must disconnect you after some time idle) is that the active-filter parameter in pppd doesn't work. And you have some icmp traffic at the ppp0 interface so I couldn't take advantage of the idle parameter of pppd. Any hints on that ? Hope I helped. Kleanthis Kremmidas System Administrator at Lambrakis Research Foundation (LRF) E-mail: kremidas@lrf.gr, kremidas@freemail.gr -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Kleanthis Kremmidas wrote:
Hi to all :)
On /etc/diald.conf and at the parameter connect you MUST use the chat script and not a ppp script. Diald starts pppd by itself. When you put it at connect then diald thinks that this is the chat script and wait for the chat script to finish. pppd doesn't exit and the diald (using alarm system call) thinks that the chat script timed out. Look at the man page also to double check it.
OK, I didn't know this about the chat.
But I changed my diald.conf to this.
mode ppp
connect '/usr/sbin/chat -f /etc/ppp/ppp.chat'
device /dev/ttyS2
speed 115200
modem
lock
crtscts
dynamic
local 192.168.1.1
remote 0.0.0.0
defaultroute
include /usr/lib/diald/standard.filter
and nothing worked any better.
This is what I get in /var/log/messages as soon as
I start diald. Immediately after typing diald -daemon.
Jan 25 17:11:20 crow diald[1679]: keepup parsing error. Got token
'tcp.ssl'. Not a known tcp service port.
Jan 25 17:11:20 crow diald[1679]: parse string: 'tcp 120
tcp.dest=tcp.ssl'
Jan 25 17:11:20 crow diald[1679]: keepup parsing error. Got token
'tcp.ssl'. Not a known tcp service port.
Jan 25 17:11:20 crow diald[1679]: parse string: 'tcp 120
tcp.source=tcp.ssl'
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap0
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap1
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap2
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap3
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap4
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap5
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap6
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap7
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap8
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap9
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap10
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap11
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap12
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap13
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap14
Jan 25 17:11:20 crow modprobe: modprobe: Can't locate module tap15
Jan 25 17:11:20 crow kernel: SLIP: version 0.8.4-NET3.019-NEWTTY-MODULAR
(dynamic channels, max=256) (6 bit encapsulation enabled).
Jan 25 17:11:20 crow kernel: SLIP linefill/keepalive option.
Jan 25 17:11:20 crow diald[1679]: Proxy device established on interface
sl0
Jan 25 17:11:20 crow diald[1679]: running '/sbin/ifconfig sl0
192.168.1.1 pointopoint 0.0.0.0 broadcast 0.0.0.0 netmask
255.255.255.255 metric 0 mtu 1500 up'
Jan 25 17:11:20 crow diald[1679]: start sl0: SIOCSIFMETRIC: Operation
not supported
Jan 25 17:11:20 crow diald[1679]: SIGCHLD[1]: pid 1697 system, status
256
Jan 25 17:11:20 crow diald[1679]: start sl0: Establishing routes for sl0
Jan 25 17:11:20 crow diald[1679]: running '/usr/sbin/ip route add
0.0.0.0 dev sl0 scope link src 192.168.1.1 metric 0 '
Jan 25 17:11:20 crow diald[1679]: SIGCHLD[2]: pid 1698 system, status 0
Jan 25 17:11:20 crow diald[1679]: running '/usr/sbin/ip route add
default dev sl0 scope link src 192.168.1.1 metric 0 '
Jan 25 17:11:20 crow diald[1679]: SIGCHLD[3]: pid 1699 system, status 0
Jan 25 17:11:20 crow diald[1679]: Changed snoop device to sl0
Jan 25 17:11:20 crow diald[1679]: Diald initial setup completed.
Jan 25 17:11:37 crow diald[1679]: SIGINT: Link down request received.
Jan 25 17:11:47 crow last message repeated 9 times
Jan 25 17:11:53 crow diald[1700]: keepup parsing error. Got token
'tcp.ssl'. Not a known tcp service port.
Jan 25 17:11:53 crow diald[1700]: parse string: 'tcp 120
tcp.dest=tcp.ssl'
Jan 25 17:11:53 crow diald[1700]: keepup parsing error. Got token
'tcp.ssl'. Not a known tcp service port.
Jan 25 17:11:53 crow diald[1700]: parse string: 'tcp 120
tcp.source=tcp.ssl'
Jan 25 17:11:53 crow diald[1700]: Unknown option 'stop'
Jan 25 17:11:53 crow diald[1700]: usage: diald [modem-device1]
[modem-device2 ...] [options...] [-- [pppd options...]]
Jan 25 17:11:53 crow diald[1700]: where valid options are:
Jan 25 17:11:53 crow diald[1700]: -f <file>
Jan 25 17:11:53 crow diald[1700]: -file <file>
Jan 25 17:11:53 crow diald[1700]: include <file>
Jan 25 17:11:53 crow diald[1700]: -m
[ppp|slip|cslip|slip6|cslip6|aslip|dev]
Jan 25 17:11:53 crow diald[1700]: mode
[ppp|slip|cslip|slip6|cslip6|aslip|dev]
Jan 25 17:11:53 crow diald[1700]: debug <debugmask>
Jan 25 17:11:53 crow diald[1700]: -daemon
Jan 25 17:11:53 crow diald[1700]: accounting-log <f>
Jan 25 17:11:53 crow diald[1700]: pidfile <f>
Jan 25 17:11:53 crow diald[1700]: fifo <f>
Jan 25 17:11:53 crow diald[1700]: tcpport <n>
Jan 25 17:11:53 crow diald[1700]: demand
Jan 25 17:11:53 crow diald[1700]: -demand
Jan 25 17:11:53 crow diald[1700]: nodemand
Jan 25 17:11:53 crow diald[1700]: blocked
Jan 25 17:11:53 crow diald[1700]: -blocked
Jan 25 17:11:53 crow diald[1700]: block
Jan 25 17:11:53 crow diald[1700]: unblock
Jan 25 17:11:53 crow diald[1700]: blocked-route
Jan 25 17:11:53 crow diald[1700]: -blocked-route
Jan 25 17:11:53 crow diald[1700]: linkname <name>
Jan 25 17:11:53 crow diald[1700]: linkdesc <description>
Jan 25 17:11:53 crow diald[1700]: authsimple <file>
Jan 25 17:11:53 crow diald[1700]: initializer <script>
Jan 25 17:11:53 crow diald[1700]: deinitializer <script>
Jan 25 17:11:53 crow diald[1700]: proxy <interface>
Jan 25 17:11:53 crow diald[1700]: scheduler [fifo|rr|other]
Jan 25 17:11:53 crow diald[1700]: priority <n>
Jan 25 17:11:53 crow diald[1700]: window <n>
Jan 25 17:11:53 crow diald[1700]: mtu <m>
Jan 25 17:11:53 crow diald[1700]: mru <m>
Jan 25 17:11:53 crow diald[1700]: metric <metric>
Jan 25 17:11:53 crow diald[1700]: local <ip-address>
Jan 25 17:11:53 crow diald[1700]: remote <ip-address>
Jan 25 17:11:53 crow diald[1700]: broadcast <ip-address>
Jan 25 17:11:53 crow diald[1700]: netmask <ip-address>
Jan 25 17:11:53 crow diald[1700]: dynamic
Jan 25 17:11:53 crow diald[1700]: sticky
Jan 25 17:11:53 crow diald[1700]: strict-forwarding
Jan 25 17:11:53 crow diald[1700]: dslip-mode <mode>
Jan 25 17:11:53 crow diald[1700]: defaultroute
Jan 25 17:11:53 crow diald[1700]: ifsetup <script>
Jan 25 17:11:53 crow diald[1700]: addroute <script>
Jan 25 17:11:53 crow diald[1700]: delroute <script>
Jan 25 17:11:53 crow diald[1700]: proxyarp
Jan 25 17:11:53 crow diald[1700]: ip-up <script>
Jan 25 17:11:53 crow diald[1700]: ip-down <script>
Jan 25 17:11:53 crow diald[1700]: ip-goingdown <script>
Jan 25 17:11:53 crow diald[1700]: device <device>
Jan 25 17:11:53 crow diald[1700]: connect <script>
Jan 25 17:11:53 crow diald[1700]: disconnect <script>
Jan 25 17:11:53 crow diald[1700]: lock
Jan 25 17:11:53 crow diald[1700]: speed <baudrate>
Jan 25 17:11:53 crow diald[1700]: modem
Jan 25 17:11:53 crow diald[1700]: crtscts
Jan 25 17:11:53 crow diald[1700]: rotate-devices
Jan 25 17:11:53 crow diald[1700]: lock-prefix <path>
Jan 25 17:11:53 crow diald[1700]: pidstring
Jan 25 17:11:53 crow diald[1700]: -pidstring
Jan 25 17:11:53 crow diald[1700]: run-prefix <path>
Jan 25 17:11:53 crow diald[1700]: path-ip <path>
Jan 25 17:11:53 crow diald[1700]: path-route <path>
Jan 25 17:11:53 crow diald[1700]: path-ifconfig <path>
Jan 25 17:11:53 crow diald[1700]: path-bootpc <path>
Jan 25 17:11:53 crow diald[1700]: path-pppd <path>
Jan 25 17:11:53 crow diald[1700]: buffer-packets
Jan 25 17:11:53 crow diald[1700]: -buffer-packets
Jan 25 17:11:53 crow diald[1700]: buffer_size <n>
Jan 25 17:11:53 crow diald[1700]: buffer-fifo-dispose
Jan 25 17:11:53 crow diald[1700]: -buffer-fifo-dispose
Jan 25 17:11:53 crow diald[1700]: buffer-timeout <n>
Jan 25 17:11:53 crow diald[1700]: route-wait
Jan 25 17:11:53 crow diald[1700]: two-way
Jan 25 17:11:53 crow diald[1700]: give-way
Jan 25 17:11:53 crow diald[1700]: connect-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: disconnect-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: redial-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: nodev-retry-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: stop-dial-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: kill-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: start-pppd-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: stop-pppd-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: first-packet-timeout <timeout>
Jan 25 17:11:53 crow diald[1700]: retry-count <count>
Jan 25 17:11:53 crow diald[1700]: died-retry-count <count>
Jan 25 17:11:53 crow diald[1700]: redial-backoff-start <count>
Jan 25 17:11:53 crow diald[1700]: redial-backoff-limit <time>
Jan 25 17:11:53 crow diald[1700]: dial-fail-limit <count>
Jan 25 17:11:53 crow diald[1700]: prule <name> <protocol> <spec>
Jan 25 17:11:53 crow diald[1700]: var <name> <spec>
Jan 25 17:11:53 crow diald[1700]: restrict <start-time> <end-time>
<weekday> <day> <month>
Jan 25 17:11:53 crow diald[1700]: or-restrict <start-time>
<end-time> <weekday> <day> <month>
Jan 25 17:11:53 crow diald[1700]: bringup <protocol-rule> <timeout>
<packet-rule>
Jan 25 17:11:53 crow diald[1700]: keepup <protocol-rule> <timeout>
<packet-rule>
Jan 25 17:11:53 crow diald[1700]: accept <protocol-rule> <timeout>
<packet-rule>
Jan 25 17:11:53 crow diald[1700]: ignore <protocol-rule>
<packet-rule>
Jan 25 17:11:53 crow diald[1700]: impulse
[<duration>,<fuzz>|<duration1>,<duration2>,<fuzz>]
Jan 25 17:11:53 crow diald[1700]: up
Jan 25 17:11:53 crow diald[1700]: down
Jan 25 17:11:53 crow diald[1700]: flushfilters
Jan 25 17:11:53 crow diald[1700]: flushprules
Jan 25 17:11:53 crow diald[1700]: flushvars
Jan 25 17:11:56 crow popper[1702]: connect from bljilek@192.168.1.1
Jan 25 17:11:57 crow diald[1679]: SIGINT: Link down request received.
Jan 25 17:12:07 crow last message repeated 5 times
Jan 25 17:12:10 crow diald[1679]: SIGHUP: modem got hung up on.
Jan 25 17:12:31 crow diald[1679]: SIGTERM. Termination request received.
Jan 25 17:12:31 crow diald[1679]: Diald is dieing with code 0
Jan 25 17:12:31 crow diald[1679]: stop sl0: Removing routes for sl0
Jan 25 17:12:31 crow diald[1679]: running '/usr/sbin/ip route del
default dev sl0 scope link src 192.168.1.1 metric 0'
Jan 25 17:12:31 crow diald[1679]: SIGCHLD[4]: pid 1705 system, status 0
Jan 25 17:12:31 crow diald[1679]: running '/sbin/ifconfig sl0 down'
Jan 25 17:12:31 crow diald[1679]: SIGCHLD[5]: pid 1706 system, status 0
Sorry about the length of this.
I'm trying to run diald with diald -daemon to try to see
what's happening but it don't print anything to the terminal.
--
B. L. Jilek
Hi, I have a SuSE 6.3 box, Network card installed and as far as I know working, I also have a Win98 box, network card installed and working. But I cannot ping one machine from the other, I have checked the cable, where next, Linux issue or Windows Issue? Many Thanks Cheers Phil Shrimpton -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
setup the card. you can tell if it is up by running ifconfig try: # ifconfig eth0 some_ip_address broadcast your_broadcast_address ryan
-----Original Message----- From: Phil Shrimpton [mailto:philshrimpton@prometrics.co.uk] Sent: Tuesday, February 01, 2000 12:28 PM To: suse-linux-e@suse.com Subject: [SLE] very newbie network quest
Hi,
I have a SuSE 6.3 box, Network card installed and as far as I know working, I also have a Win98 box, network card installed and working.
But I cannot ping one machine from the other, I have checked the cable, where next, Linux issue or Windows Issue?
Many Thanks
Cheers
Phil Shrimpton
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
From: Ryan Yagatich [mailto:ryagatich@csn1.com]
setup the card. you can tell if it is up by running ifconfig try:
# ifconfig eth0 some_ip_address broadcast your_broadcast_address
Hi, Done this... ifconfig eth0 192.168.110.1 broadcast 192.168.110.255 netmask 255.255.255.0 up route add -net 192.168.110.0 netmask 255.255.255.0 eth0 No results were displayed, but no errors either. I can ping this address on the Linux box, both as an IP or by the Hostname, but the windows box does not want to know. Cheers Phil
-----Original Message----- From: Phil Shrimpton [mailto:philshrimpton@prometrics.co.uk] Sent: Tuesday, February 01, 2000 12:28 PM To: suse-linux-e@suse.com Subject: [SLE] very newbie network quest
Hi,
I have a SuSE 6.3 box, Network card installed and as far as I know working, I also have a Win98 box, network card installed and working.
But I cannot ping one machine from the other, I have checked the cable, where next, Linux issue or Windows Issue?
Many Thanks
Cheers
Phil Shrimpton
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
At 05:28 PM 2/1/00 +0000, Phil Shrimpton wrote:
I have a SuSE 6.3 box, Network card installed and as far as I know working, I also have a Win98 box, network card installed and working.
But I cannot ping one machine from the other, I have checked the cable, where next, Linux issue or Windows Issue?
Hard to say. Are you connecting them from one ethernet port to the other ethernet port directly? If so, are you using a crossover cable? If not, you'll need to get one. Otherwise you'll have to run the connection through a hub or switch. Of course, this is an over-generalization but it gets to the point. Does your Win98 box have TCP/IP loaded? I would imagine it does, just checking. Are both machines configured for the same network with the same subnet mask? Again, an over-generalization for you sticklers out there. If you have covered each of these things (you are using the appropriate cable, TCP/IP is loaded and the IP stacks are configured properly) then are you getting a link light on the connections? If so, what happens when you try to ping one machine from the other. Have you tried the ping in both directions? Do you see any blinking on the network cards when you attempt a ping? As you can see, more information is required before much diagnosis can be given. Regards, Troy Denkinger -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi, I can write code in just about any language, but give me a bit of cable and I am scratching my head, bear with me on this one..
Hard to say. Are you connecting them from one ethernet port to the other ethernet port directly? If so, are you using a crossover cable? If not, you'll need to get one. Otherwise you'll have to run the connection through a hub or switch. Of course, this is an over-generalization but it gets to the point.
Linux box - PCI Western Digital 10Mb Ethernet Card BNC Connection Win98 box - PCMCIA 10Mb Ethernet BNC Connection Cable - co-axal, T connectors on each end, each with a terminator. No Hubs or switches...
Does your Win98 box have TCP/IP loaded? I would imagine it does, just checking.
Yes.
Are both machines configured for the same network with the same subnet mask? Again, an over-generalization for you sticklers out there.
erm... I have set the IP address and netmask of the Linux box. Not done anything on the windows box, should I, if so what and where?
If you have covered each of these things (you are using the appropriate cable, TCP/IP is loaded and the IP stacks are configured properly) then are you getting a link light on the connections?
I getting a flashing 'ACT' light on the windows box, but not 'LINK' There are no lights on the linux box
If so, what happens when you try to ping one machine from the other.
Nothing
Have you tried the ping in both directions?
Yes. Nothing
Do you see any blinking on the network cards when you attempt a ping?
Only the ACT light on the windows box. Many, many thanks for the quick responses.. Cheers Phil -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
At 06:15 PM 2/1/00 +0000, Phil Shrimpton wrote:
Linux box - PCI Western Digital 10Mb Ethernet Card BNC Connection Win98 box - PCMCIA 10Mb Ethernet BNC Connection Cable - co-axal, T connectors on each end, each with a terminator. No Hubs or switches...
Okay, you should be good to go here. We were assuming you were using 10BaseT or similar setup. The setup you describe should be fine.
erm... I have set the IP address and netmask of the Linux box. Not done anything on the windows box, should I, if so what and where?
On the Win98 box, do "Start -> Run... -> winipcfg -> OK" and see what you get. In the dropdown, make sure you select the network interface you're trying to connect the two boxes to. Do you see any IP address etc there? If not, you need to setup a static IP on the box. If you do see stuff here, it should roughly match the information you configured the Linux box with (IP address in the same subnet with the same subnet mask). If you see nothing in winipcfg, then you'll need to enter it by hand. Right click "Network Neighborhood" on the desktop and select "Properties." Select the "TCP->{your nic here}" line and click "Properties." You can setup all the IP parameters here. Click okay all the way out and you'll be asked to reboot. Reboot. Now, see what happens.
I getting a flashing 'ACT' light on the windows box, but not 'LINK' There are no lights on the linux box
If you aren't getting a link light, you're outta luck usually. If you get the stack configured on the Win98 box and the Linux box and still nothing works, you might start looking at the hardware, but that would be the last thing to check in my opinion. Regards, Troy Denkinger -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
From: Troy Denkinger [mailto:troy@whadda.com]
Hi,
Right click "Network Neighborhood" on the desktop and select "Properties." Select the "TCP->{your nic here}" line and click "Properties." You can setup all the IP parameters here. Click okay all the way out and you'll be asked to reboot. Reboot.
Bingo, I had my windows box set to obtain a IP address dynamically, just gave it an IP address and set the subnetmask the same as the Linux box and I can now ping both ways... Still not getting a LINK light on my Windows Box, but I entered the Linux box IP in my browser and got the Apache home page, but still no link light. I guess my next step to be able to map a drive in Windows explorer is to set up DNS? Then set up Samba? I have briefly read all the how-tos on this, but does anyone know of a complete idiots hand-holding guide, just so I don't bug every one will silly questions? Cheers Phil -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
At 07:07 PM 2/1/00 +0000, Phil Shrimpton wrote:
Bingo, I had my windows box set to obtain a IP address dynamically, just gave it an IP address and set the subnetmask the same as the Linux box and I can now ping both ways...
This is the default stance for a Win98 box.
Still not getting a LINK light on my Windows Box, but I entered the Linux box IP in my browser and got the Apache home page, but still no link light.
Hmm, well, if you're able to ping both ways, you just have a dead link light.
I guess my next step to be able to map a drive in Windows explorer is to set up DNS? Then set up Samba?
Mmm, you shouldn't need DNS. You can map a share to an IP address if you want and DNS is just going to complicate the issue. I'm still trying to get Samba working properly myself; I found useful information at the samba website and in the O'Reilly Samba book. I was actually able to map and browse a remote Win98 machine by using the Samba docs, but I haven't gotten printing working. Use Swat, the web based configuration utility for Samba. Good luck. Regards, Troy Denkinger -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
From: Troy Denkinger [mailto:troy@whadda.com]
Bingo, I had my windows box set to obtain a IP address dynamically, just gave it an IP address and set the subnetmask the same as the Linux box and I can now ping both ways... I guess my next step to be able to map a drive in Windows explorer is to set up DNS? Then set up Samba?
Mmm, you shouldn't need DNS.
Yes, I understand that now. Started to follow an idiots guide to setting up Samba, and some how seam to have lost my eth0. I tried setting it back up in YAST, but it just won't stay. I have gone backwards through the Samba set-up instructions to try to undo everything, with know luck. Any ideas what I have done? Cheers Phil -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Tue, 01 Feb 2000, Phil Shrimpton wrote:
Started to follow an idiots guide to setting up Samba, and some how seam to have lost my eth0. I tried setting it back up in YAST, but it just won't stay. I have gone backwards through the Samba set-up instructions to try to undo everything, with know luck.
Wow, that sounds frustrating. So, if you go into Yast and select "System Administration -> Integrate Hardware Into System -> Configure Network Device" and try to enter information for eth0 and then select "Continue." the changes aren't saved? That's strange and outside my experience. I hope someone else here might have a clue. Sorry I can't be more help than that. If you do get everything back in order, take a look at the SMB HowTo here: http://www.linuxdoc.org/HOWTO/SMB-HOWTO.html#toc1 This is about all I used to get the thing working to some extent. Good luck. Regards, Troy Denkinger -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
From: Troy Denkinger [mailto:troy@whadda.com]
Hi,
Started to follow an idiots guide to setting up Samba, and some how seam to have lost my eth0. I tried setting it back up in YAST, but it just won't stay. I have gone backwards through the Samba set-up instructions to try to undo everything, with know luck.
Wow, that sounds frustrating.
So, if you go into Yast and select "System Administration -> Integrate Hardware Into System -> Configure Network Device" and try to enter information for eth0 and then select "Continue." the changes aren't saved?
No changes are saved, and there is no update script run etc. The Samba instructions told me to add a few lines to various *.conf files, but I have removed all of these. I have even uninstalled Samba completely, to try and start again, but still no luck.
If you do get everything back in order, take a look at the SMB HowTo here:
I found an online version of 'Using Samba' by 'Robert Eckstein, David Collier-Brown, Peter Kelly'. This is very much a step-by-step idiots guide, with lots of pictures etc. http://www.kneschke.de/projekte/ksamba/using_samba/inx.html Cheers Phil -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Are you connecting via a hub or a crossover? Do you have link lites on each nic? Cliff Pankonien System Administrator Delaware.Net, Inc. cliff@delaware.net Visit our Tucows Linux mirror at http://delaware.linux.tucows.com On Tue, 1 Feb 2000, Phil Shrimpton wrote:
Hi,
I have a SuSE 6.3 box, Network card installed and as far as I know working, I also have a Win98 box, network card installed and working.
But I cannot ping one machine from the other, I have checked the cable, where next, Linux issue or Windows Issue?
Many Thanks
Cheers
Phil Shrimpton
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (6)
-
bljilek＠bigfoot.com -
cliff＠delaware.net -
kremidas＠lrf.gr -
philshrimpton＠prometrics.co.uk -
ryagatich＠csn1.com -
troy＠whadda.com