|
|
| shanelai 2002-07-08, 3:47 pm |
| I'm bridging 2 ethernet segments across a frame-relay link using DLSw. I've got 2 Windows XP machines running netbeui (you can install netbeui off a separate directory on the CD) on each end of the DLSw link to test it. I've found that I can browse files, but once I try to copy a file, I get a message saying that the source file or disk cannot be read. "sh dlsw circuit" shows an active circuit created. Any insight to this?
My config-
R1:
dlsw local-peer peer-id 140.3.1.1 promiscuous
dlsw remote-peer 0 tcp 140.3.2.2
dlsw bridge-group 1
!
interface Loopback0
ip address 140.3.1.1 255.255.255.0
!
interface Ethernet0
no ip address
bridge-group 1
!
bridge 1 protocol ieee
R2:
dlsw local-peer peer-id 140.3.2.2 promiscuous
dlsw remote-peer 0 tcp 140.3.1.1
dlsw bridge-group 1
!
interface Loopback0
ip address 140.3.2.2 255.255.255.0
!
interface Ethernet0
no ip address
bridge-group 1
!
bridge 1 protocol ieee | |
| dumbut 2002-07-08, 10:01 pm |
| reboot your pc.. | |
|
| Couldn't you just tell that he had an MCSE!!
Couldn't resist it, sorry. | |
| shanelai 2002-07-09, 6:20 am |
| LOL! Seriously? That's one thing I haven't tried yet.  | |
| cahillrobert 2002-07-09, 6:43 am |
| quote:
bridging 2 ethernet segments across a frame-relay link
How is your frame-relay serial link configured? | |
| shanelai 2002-07-09, 9:21 am |
| quote:
Originally posted by cahillrobert
How is your frame-relay serial link configured?
Nothing out of the ordinary:
int s0
ip add 140.3.12.1 255.255.255.0
no frame inverse-arp
frame map ip 140.3.12.2 102 broadcast
router eigrp 1
net 140.3.0.0 | |
| shanelai 2002-07-10, 10:39 am |
| In case anyone's wondering, setting the mtu size manually with the "lf" keyword in the remote peer statement solved the problem. | |
| cahillrobert 2002-07-10, 2:55 pm |
| Thanks for the update.
I was still trying to figure this out w/o any luck.
Do you have any idea why this was needed?
What prompted this thought?
Always curious.
- Bob | |
| dumbut 2002-07-10, 8:56 pm |
| quote:
Couldn't you just tell that he had an MCSE!!
That's why you don't have an mcse. | |
| clever rabbit 2002-07-17, 5:44 pm |
| quote:
Originally posted by shanelai
In case anyone's wondering, setting the mtu size manually with the "lf" keyword in the remote peer statement solved the problem.
I've met the similar problem when I configured dlsw. Why don't you try to get the "key" from the groupstudy CCIE mail list?
If you haven't joined it yet, I suggest you to join as soon as possible. It's necessary for everyone who is working on CCIE.You will solve all of your confused problems. | |
| dumbut 2002-07-19, 5:49 pm |
| quote:
I've met the similar problem when I configured dlsw. Why don't you try to get the "key" from the groupstudy CCIE mail list?
Sometime would be a better idea to find out oneself then go for a easy answer. |
|
|
|